23

Y'all ever notice how the size and complexity of a project is a source of pride for those whom created the project, and a source of dread for those who need to maintain it?

Comments
  • 3
  • 0
    if u ever notice AIK in the comments there is a chance that is part of my legacy. Instead of cursing me pls ask me what is torture u and I'll do my best to remember my reasoning @ that time. thks =]
  • 6
    I'm not proud of leaving behind unmanageable code, but i get what you mean
  • 3
    I had that in one of my projects where I could have gone with some nifty digital filtering shit... but just simulating basic first order RC-filtering already did the job and would be a lot easier to understand for future co-workers.
  • 3
    Literally feeling it rn

    I won't be able to recreate the projects i built myself in the same manner as i did during the first iteration
  • 3
    Are you calling my code too complicated?
  • 3
    Honestly: no. Where I've worked, a slim and simple codebase has always been the goal, "deleting code is better than adding code" has been a mantra and when I've inherited a codebase the creators always apologised for how it was more complex than it should be..

    Maybe I've been fortunate to work with a lot of seniors.

    But inevitably codebases tend to grow with time
Add Comment