Technical debt isn't new. AI just put it on a credit card.
Technical Debt / 4 min

Technical debt isn't new. AI just put it on a credit card.

Every shortcut in software gets paid back eventually, with interest. AI coding tools don't remove that cost - they just let teams take on debt faster than anyone notices.

Debt is the right word, not a metaphor

Technical debt works exactly like financial debt: you take a shortcut to ship something now, and the difference between the shortcut and the proper version doesn't disappear, it sits there collecting interest until someone pays it down or the project collapses under it. Deloitte's 2026 Global Technology Leadership Study puts the number at 21 to 40 percent of total IT spending, and CISQ estimates the accumulated principal across US software at $1.52 trillion. That's not a rounding error, it's a second budget nobody approved.

AI didn't create the problem, it sped up the loan approval

Code generation tools make it trivial to produce working features in minutes that used to take days. The code runs, the demo looks great, everyone moves on. What doesn't show up in the demo is whether anyone understands what was generated, whether it fits the rest of the system, or whether it was reviewed the way a human-written pull request usually is. One estimate puts the hidden annual cost for a 20-engineer team using unmanaged AI code generation at $1.16 million - the equivalent of paying four senior engineers whose entire job is fixing what the other sixteen shipped.

Compiling isn't the same as understanding

"It works" is the lowest bar code can clear, and AI-generated code clears it easily, every time. The bar that actually matters is whether a person on the team could explain why it was written that way, change it safely six months from now, or hand it to someone new without a guided tour. A pile of code nobody fully understands isn't a feature, it's a liability sitting in the codebase waiting for the day someone has to touch it under pressure.

The ACS approach

We use AI tools too - pretending otherwise would be dishonest. What we don't do is ship anything a human hasn't actually read and could explain back. Every AI-assisted change goes through the same review a human-written one would, because the point was never "did it compile", it was always "can we still move fast on this in a year." Speed that nobody can account for later isn't speed, it's debt with better marketing.