4 ms·
> making code overly DRY and wrong abstractions coupling unrelated parts of the system unnecessarily I would say that's just bad engineering due to lack of ins
by spdionis 9y ago
> making code overly DRY and wrong abstractions coupling unrelated parts of the system unnecessarily
I would say that's just bad engineering due to lack of insight or experience. DRY is the most simple and most dangerous principle (or "best-practice") of them all, because when it goes wrong it's the one that hurts the most.
- allyjweir 9y agoYes I agree. Bad engineering led them to not accepting the reality that technical debt is unavoidable. In a misguided attempt to avoid it, they overengineered ironically leading to more debt than might otherwise have accrued.