Technical Debt
Type: Systems & Dynamics
Local HTML: technical_debt.html
Definition
Shortcuts in code or systems that save time now but cost more later. Like financial debt — you borrow speed, pay back with interest.
Ward Cunningham coined the term: Shipping messy code is like borrowing money. You can do more now, but pay interest forever.
Why It Matters
Software: Quick fixes accumulate. Eventually, changing anything breaks everything. Organizations: Process shortcuts become permanent. “Temporary” workarounds last decades. Personal: Skipping exercise, eating poorly, ignoring maintenance — debt accrues. Civilization: Infrastructure decay, climate inaction, education gaps — societal technical debt.
Types of Debt
| Type | Description |
|---|---|
| Prudent | Taken knowingly, with plan to repay |
| Reckless | Taken unknowingly or carelessly |
| Deliberate | Conscious choice for speed |
| Inadvertent | Discovered after the fact |
The Interest
- Slower development — Changes take longer
- More bugs — Complexity breeds errors
- Knowledge silos — Only old-timers understand
- Attrition — Good developers leave
- Rewrite or die — Eventually, total replacement needed
Managing Debt
- Track it — Know what you owe
- Pay incrementally — Refactor as you go
- Budget for it — Allocate time to reduce debt
- Don’t take on more — Resist pressure for shortcuts
Related Biases
- Hyperbolic Discounting — Now > later
- Optimism Bias — “We’ll fix it later”
- [[Planning Fallacy** — Underestimating repayment cost
Audio
Podcast episode: Technical Debt
Part of the Cognitive Bias Reference