> you cannot split up a large established codebase without first understanding it I’ve seen enough wild rewrites to realise they often create more chaos than t

> you cannot split up a large established codebase without first understanding it I’ve seen enough wild rewrites to realise they often create more chaos than they solve. Over time, I’ve come to view older codebases as living libraries of knowledge, rather than something to refactor out of existence. Every quirk usually has a backstory or a user need behind it. It’s less about ripping everything apart and more about respecting those conventions so you can make use of them.