What Is Technical Debt?
What technical debt is, when it happens, and how to manage it so it doesn't drag your software down.
Technical debt is a term used in the software industry to describe the long-term cost of decisions that speed up delivery in the short term but may cause technical problems later. It's the extra work you'll have to do down the road to fix shortcuts taken today — or to align the code with the good practices that were skipped.
A concrete example
Imagine a tight deadline to ship a new feature. To hit the date, the team decides not to invest in robust tests or refactor the code for readability. The feature ships on time — but the software becomes harder to maintain and evolve, and that debt starts accruing interest.
Technical debt isn't inherently bad
In some cases, taking on technical debt is a conscious, justified decision — when an experiment needs to ship fast, when the team is betting on a market hypothesis, or when validating first makes more sense than polishing.
What matters is that the team:
- Knows it's taking on debt (conscious, not accidental).
- Documents the shortcuts being taken.
- Has a plan to pay the debt before it becomes a blocker.
- Reserves capacity in future sprints for the refactors and tests that were skipped.
Managed technical debt is leverage. Forgotten technical debt is a brake.
March 9, 2023 · Brazil