What Is Technical Debt?
Technical debt is the implied future cost of choosing a quick, easier solution now instead of a better, more time-consuming approach — like financial debt, i...
Published October 8, 2026
Technical debt is the extra future cost created when a team chooses a quick or imperfect solution now. Like financial debt it accrues interest: every change gets slower until it is paid down.
The concept
Debt can be deliberate (ship now, clean later) or accidental (we did not know better). Typical forms: duplicated code, missing tests, outdated dependencies and unclear architecture.
Not all debt is bad; the problem is unmanaged debt. Track it and repay it regularly.
Interest builds up
Practical examples
Track it
// TODO(debt): replace polling with webhooks — #482Pay it down with the boy-scout rule
Leave the code a bit cleaner than you found it in every change.Dependency debt check
npm outdated
composer outdatedCommon mistakes
- Never scheduling time to repay it.
- Hiding it from stakeholders.
- Large rewrites instead of incremental improvement.
Key takeaways
- Shortcuts cost interest later.
- Track and prioritise debt.
- Repay in small steps.
FAQ
How do I explain it to managers?
As compounding slowdown: each feature takes longer until it is addressed.
Is all debt bad?
No, deliberate short-term debt can be a sound trade-off.