rjromero

When you first start a project, the coding space seems “open” and you can’t do anything offensive or messy, as time goes on however this window really closes and you end up having to code within more and more layers of complexity. Towards the end you’re really down the pipe and you are writing code between 6 different classes inside deep nested functions and checking callbacks, etc...

I’m sure you know the feeling. It sucks. It’s really easy to start a project and get going but over time it’s just really really difficult to manage a growing codebase. In fact I’ll get 90% of the easy code done first and love it and then procrastinate the last 10% forever.

So how do you prevent this? What programming paradigms do you use? For me at least this is really a problem with giant OOP projects where it can get sticky between the classes and who is a delegate of what and who calls back to what.

How does anything ever get done in gigantic codebases for operating systems and planes for example? Maintaining a codebase of that size honestly sounds like a miracle.