A team names a concept “teams” early on, later decides it should be “groups,” and changes only the label on screen because renaming it across the codebase would take a week. Each new engineer then pays a little interest in confusion until someone does the rename. Ward Cunningham coined the metaphor in 1992: a little debt speeds development as long as it is paid back promptly, and the danger comes when it is not.
AI adds three angles. First, machine learning systems build up their own kinds of debt. Sculley and colleagues at Google argued in 2015 that a model’s behavior depends on its data, its pipelines and the systems that consume its output, so changing one part can quietly change the rest. Second, coding agents can pay debt down. Simon Willison argues that the simple but tedious fixes teams keep postponing are a good fit for agents. Third, agents can create debt faster than before, because code that is cheap to write still has to be reviewed, understood and maintained.
In episode 36 at 13:21, ChatPRD’s Claire Vo says people underestimate “the ability for AI to accelerate cleaning up your gnarliest parts of tech debt,” such as framework migrations that used to take 18 to 24 months. She adds that work to make a repository easier for AI, like a local setup that does not take three days, helps human engineers too (14:18). The episode was sponsored by Galileo; the outro points listeners to Galileo’s YouTube channel at 42:24.
In episode 68 at 27:40, Chainguard’s Dan Lorenc says “people have to pay off a lot of tech debt” to keep up with AI-found vulnerabilities, and suggests rethinking old assumptions about backward and API compatibility because the same tools are good at upgrading software. Svix and Walrus Memory are the season’s presenting sponsors; the Svix read is at 22:02.
In episode 78 at 37:08, Svix CEO Tom Hacohen wonders whether “maybe technical debt will remain a thing” even with far more machine intelligence on hand. Conor replies that agents could be always on, paying debt down as it is created, yet their continual output can just as easily scale the problem (37:34). Episode 78 is sponsored by Svix, the Season 4 presenting sponsor; the sponsor thank-you is at 1:56.
Hear it from the guest
“The ability for AI to accelerate cleaning up your gnarliest parts of tech debt”
“People have to pay off a lot of tech debt”
“Maybe technical debt will remain a thing”
Quotes lightly edited to remove filler words.
Sources
- Ward Cunningham: The WyCash Portfolio Management System (OOPSLA 1992 experience report) — The report that introduced the metaphor: shipping first-time code is like going into debt, which speeds development if it is paid back promptly with a rewrite, while time spent on not-quite-right code counts as interest; checked October 24, 2026.
- Sculley et al.: Hidden Technical Debt in Machine Learning Systems (NeurIPS 2015) — Argues that machine learning systems carry extra, system-level maintenance costs beyond ordinary code, including boundary erosion, entanglement, hidden feedback loops, undeclared consumers and data dependencies; checked October 24, 2026.
- Simon Willison: AI should help us produce better code — Argues that coding agents suit debt fixes that are simple but time-consuming, such as renaming a concept everywhere or splitting a huge file, and that shipping worse code with agents is a choice; checked October 24, 2026.
Go deeper
From the conversation
-
How AI Velocity is Rewriting the Rules for Engineering Leaders | ChatPRD's Claire Vo -
Time to Exploit is Negative: AI Broke the Patch Cycle | Dan Lorenc, Chainguard -
What Breaks When Agents Become the Customer | Svix CEO Tom Hacohen -
Using AI to Modernize Your Legacy Applications | MongoDB’s Rachelle Palmer -
Stop Token Maxxing: Find Where AI Actually Pays Off | Jiaona Zhang, Laurel -
How Intercom Cut $250K/Month by Ditching GPT for Open Models | Fergal Reid -
AI in 2025: Agents & The Rise of Evaluation-Driven Development | Galileo's Yash Sheth & Atindriyo Sanyal -
Your Best AI Engineer Might Have the Worst Metrics | Sonar CTO Andrea Malagodi