A major side effect of introducing me to your codebase is refactoring and overhaul. A cardinal philosophy of mine is code reuse. In all my years inheriting codebases, I've never encountered one where the predecessor grasps the concept of abstraction. Tradeoff is it takes me longer to start implementing new functionality

The DRY zealots generate thousands of lines of difficult to maintain logic bombs just to avoid a simple to understand logic repeat.

Unless you're talking about the 10k copy and paste monstrosities... *Shudder*

@lungdart I have seen people create walled gardens making it impossible to reuse code without copying the code. I asked my boss "Why?" and he shrugged and said "I don't know." And that is just ONE style of code we have in the codebase.

lol

I will improve things, but I just get good at making things better incrementally.

@lungdart it's more about rejecting to perpetuate or act as corollary to a poor codebase. It's not about having a higher moral standing, I genuinely can't. Why would I start copy pasting code everywhere instead of refactoring usages of the same functionality into a unified, reusable method spanning across the system. That is one of the pillars of software engineering, not typing or copying everything all the time. Always annoys me to see such low-level thinking littered everywhere. It doesn't even show that the developer properly understands toolset in their arsenal. Imagine if all the utility methods in your favourite language/framework had to be spread out each time instead of being in the nifty format you currently summon it in