Why 'Technical Debt' Is the Wrong Metaphor for Messy Code

A software developer argues that the widely used term 'technical debt' is a misleading metaphor because, unlike a real loan, it has no fixed number, was never consciously agreed upon, and cannot be fully repaid. Ward Cunningham, who coined the term in 1992, originally meant it to describe deliberate shortcuts taken to accelerate learning, not poorly written code in general. The developer notes that not all problematic code carries equal cost — files that are rarely touched may cause no slowdown for years, while a small, frequently changed file can consistently drain productivity. Instead of framing issues as debt, the author recommends describing concrete friction points, such as how long a specific change takes or which planned features are blocked by current architecture. The piece concludes that what teams call technical debt is better understood as the growing gap between an aging system and an evolving world, one managed through ongoing maintenance rather than a final payoff.