TECH Signal 400
Calling sloppy code "tech debt" misleads business stakeholders about cost and intent
↗
An essay argues that most of what developers label "technical debt" is actually just mess, sloppy work, lack of skill, or aesthetic preference, and that the financial-debt metaphor misleads because real debt is predictable and businesses deliberately take it on.
If you use "tech debt" with non-technical stakeholders, they may hear an admission of poor craftsmanship rather than a deliberate tradeoff, eroding trust. The metaphor also implies the cost of a decision was understood when it was made, which the author says is rarely true for technical choices.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Financial debt is predictable and businesses deliberately take on an optimal non-zero amount, but most technical decisions' costs are not understood until later.
Much of what gets called "tech debt" doesn't speed up development at all, slow or unreliable tests reflect a lack of craft, not a deliberate loan from the future.
Some "debt" is purely aesthetic preference, as when a team consolidates container images and then later splits them again, with neither version being wrong.
THE CLUSTER