Code is a liability. Not writing code is one of the best things a developer can do on any particular day, aside of course from deleting it ;)
Quite an effective approach:
What a boring trite reply. All of this is analogous to badly written spaghetti code. And yes, you can absolutely avoid all of this if you know what you're doing.
Not trite at all. Bad code and bad architectures are a reality. You can fix them in theory, but that takes a lot of time and needs to be done incrementally. In the meantime, you have to live with the problem at hand.
Reminds me of my favorites debugging technique. It's super fast: Don't write any bugs!