ayo/blog
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

edit post

Browse source
This commit is contained in:
Ayo 2023-05-29 21:02:10 +02:00
parent ccb0edd17e
commit 5839d53722
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_posts/2023-05-29-mind-numbing-technical-debt.md
View file

@ -29,8 +29,6 @@ I kind of expected this. Big changes are always difficult.
## This Could've Been Avoided, Could It? ## This Could've Been Avoided, Could It?
Now that the conflicts on my branch are gone and tests are running again (🤣) -- oooh Lunch Time already?! -- Let's talk about the first reason this undertaking is such a pain in the a**les (ankles).
In the summer of 1985, [Back to the Future](https://en.wikipedia.org/wiki/Back_to_the_Future) hit the cinemas and became the highest-grossing film of the year. Everyone dreamed of somehow being able to fix their bad status quo by traveling to the past and maybe tweaking small details of their life. I still wasn't alive back then, but I sure still liked the movie after I watched it recently--and the core concept behind it really makes one think... In the summer of 1985, [Back to the Future](https://en.wikipedia.org/wiki/Back_to_the_Future) hit the cinemas and became the highest-grossing film of the year. Everyone dreamed of somehow being able to fix their bad status quo by traveling to the past and maybe tweaking small details of their life. I still wasn't alive back then, but I sure still liked the movie after I watched it recently--and the core concept behind it really makes one think...
What if I was at the beginning of this project? What could have I done to prevent this codebase from giving my future self all this trouble? What if I was at the beginning of this project? What could have I done to prevent this codebase from giving my future self all this trouble?