"Technical debt" might be one of the most successful terms ever coined in software engineering.
Not because it solved the problem. Technical debt is still everywhere. But it fundamentally changed the conversation. Before the term existed, engineers struggled to explain why seemingly harmless shortcuts eventually become expensive. Calling it technical debt gave business leaders a language they already understood. Debt accumulates interest. Debt carries risk. Debt demands attention.
It was a brilliant metaphor.
The metaphor didn't eliminate technical debt, but it changed how organizations think about it. Today, no serious engineering organization questions whether technical debt exists. The conversation has shifted from Is this a real problem? to What should we do about it? That's the power of language.
Today, our industry has another equally pervasive problem.
