📎 Webclip
Defining Technical Debt
The article defines technical debt as code that is more expensive to maintain than it should be. It treats that definition as broad enough to include lost productivity, quality risks, and morale problems, while also showing that debt can be a deliberate strategic choice under pressure.
Reading notes#
- Technical debt is described as unnecessary complexity, duplication, subpar code, or other deficient code that creates risks in time, quality, security, morale, or similar areas.
- Adam Tornhill’s definition is preferred because it is simple and broad: code that is more expensive to maintain than it should be.
- The article says technical debt can come from mistakes, lack of skill, or shortcuts.
- It also says technical debt can be strategic when teams need an urgent fix or face deadlines that force corner-cutting.
- The financial metaphor presents debt as a loan and the harmful effects as interest.
- The farming metaphor compares repeated feature delivery without rest to depleted soil and lower returns over time.
- The article says software atrophy can create technical debt when code stays on an older framework while the platform around it advances.
- The pipes and arteries metaphor compares bad code buildup to corrosion or plaque that slows flow and can cause major failures.
- The closing section says technical leadership must communicate technical debt clearly and balance it against hiring, architecture, business goals, infrastructure costs, and risk communication.
