Technical Debt
Noun · Hacker Culture · Origin: 1992
Definitions
Technical Debt is a software engineering metaphor coined by Ward Cunningham describing the accumulated cost of choosing quick, expedient solutions over better approaches that would take longer to implement. Like financial debt, technical debt accrues interest: the longer shortcuts remain in the codebase, the more expensive they become to fix and the more they slow down future development. Technical debt takes many forms, including duplicated code, missing tests, outdated dependencies, poor documentation, tightly coupled modules, and hardcoded values. Some technical debt is intentional and strategic (shipping faster to meet a deadline with a plan to refactor), while some is unintentional (caused by inexperience or evolving requirements). Managing technical debt requires making it visible through tracking, allocating regular time for repayment, and making informed tradeoff decisions. Ignoring it leads to declining developer productivity, increasing bug rates, and eventually a codebase that resists any change.
In plain English: Shortcuts taken during development that save time now but create more work later — like only cleaning the parts of your house that guests can see.
Example: "We took on some technical debt to ship by Friday. That was three years ago. We're still paying interest."
Etymology
- 1992
- Ward Cunningham introduces the debt metaphor at OOPSLA conference
- 2003
- Martin Fowler's article formalizes the technical debt quadrant
Origin Story
A financial metaphor that changed how we talk about code quality
In 1992, Ward Cunningham was trying to explain to his financially-minded boss why the codebase needed refactoring. He reached for a metaphor the business side would understand: debt.
Just as financial debt lets you buy something now and pay later (with interest), Cunningham argued, quick-and-dirty code lets you ship faster now but makes every future change more expensive. The 'interest' on technical debt compounds: the longer you wait to pay it down, the more costly refactoring becomes.
The metaphor resonated powerfully and spread through the industry. By the 2010s, 'technical debt' had become universal vocabulary in standups, retrospectives, and engineering leadership discussions. It remains one of the most successful bridges between engineering and business thinking.
Coined by: Ward Cunningham
Context: OOPSLA '92 Conference, Portland
Fun fact: Cunningham later clarified that technical debt was specifically about the gap between your evolving understanding and the code — not about writing sloppy code deliberately.