Technical debt is the future cost of an explicit architectural decision to use less-than-ideal design or code so value can be delivered sooner. Like financial debt, it creates an obligation to repay through later work. section 3.1.5
The distinction from ordinary cruft matters: deliberate debt acknowledges stakeholders, risks, and consequences, while implicit design problems may arise without awareness and create unexpected risks. Making decisions explicit helps teams manage the resulting trade-offs. section 3.1.5
Unpaid technical debt can lead to:
- Inability to add new functionality. section 3.1.5
- Longer implementation and push-to-production times. section 3.1.5
- More bugs when developers rely on hacks. section 3.1.5
- Frustration, communication breakdown, and resistance within the group. section 3.1.5
