Technical debt
Technical debt is the future cost incurred by fast or approximate development choices that favour the short term. Like financial debt, it accrues interest: the more it builds up, the slower, riskier and more expensive changes become. Keeping it under control is essential to a software product's longevity.
Where does technical debt come from?
It accumulates for many reasons:
- tight deadlines that encourage shortcuts;
- a lack of automated tests;
- duplicated or poorly structured code;
- outdated dependencies and technologies;
- missing documentation and high team turnover.
Deliberate or inadvertent debt?
| Type | Origin | Handling |
|---|---|---|
| Deliberate | Conscious choice to ship faster | Acceptable if tracked and repaid |
| Inadvertent | Lack of skill or rigour | Prevent via good practices |
| Bit rot | The technical context evolves | Monitoring and regular updates |
Questions fréquentes
No. Taking on deliberate debt to ship faster can be a sound strategic choice, provided it is documented and repaid later. It is unmanaged, inadvertent debt that becomes dangerous.
Through regular refactoring, sufficient test coverage, code reviews, dependency updates and explicit tracking of debt in the backlog. Consistency matters more than occasional large clean-up efforts.
Through code-quality analysis tools (complexity, duplication, test coverage) and indicators such as time spent fixing bugs or the slowdown in delivering new features.
A software project to scope and build? We design bespoke software aligned with your real needs.
See our custom software expertiseDéfinitions liées