It's not about that either ... it's about things that were put off, generally for valid reasons at the time.
> It's never the new feature that's the problem.
What do you mean by "problem"? Many new features are inherently problematic.
> If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.
That would only apply to waterfall development with infinite foresight. In the real world, wise people employ the YAGNI principle.
Edit: Is saying "bad design" or "ineffective design" going to lead to some fearful confrontation?
Where would you substitute "bad design" or "ineffective design" into the comment?
Perhaps this will help: http://wiki.c2.com/?TechnicalDebt
> Perhaps this will help: http://wiki.c2.com/?TechnicalDebt
Seriously, it won't. That's the point. People overload these words. It's a cute ideal definition though.
Over and out.
P.S. Yeah, go ahead and downvote me, troll.
Edit: I apologize for beating a dead horse.
Is it obvious to you that it's not just me?
It's never the new feature that's the problem. If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.