Every cleanup process you have was designed for human-speed mess-making. AI agents just have a “hit the nitro” button.
A recent piece on pmdata.substack.com coined a term I can't stop thinking about: "AI slop debt." It's about what happens when tools like Claude Code and Lovable generate mountains of functional-but-soulless code. And it nails something most of us are feeling but haven't named yet.
The Speed Problem Isn't New. The Scale Is.
Technical debt has been around ever since we started delivering software. We've always cut corners, shipped the hacky thing, promised to fix it later. It was acceptable. Humans generate tech debt at a pace humans can (theoretically) clean up.
AI agents are not concerned about “later.” They write code so fast that your backlog is obsolete before the next sprint planning.
Nobody Owns This Code
The author of pmdata compares it to taking on unowned critical code at SoFi. You’ve been there. Some system is load-bearing, nobody wrote docs, the original author left, and now it’s your problem.
AI slop debt is that scenario, except it's every file. The "original author" was a probabilistic model that doesn't remember writing it. There's no one to Slack. There's no institutional memory. There's just... output.
Here is what exacerbates the situation:
→ No ownership. Nobody feels responsible for AI-generated code the way they do for code they wrote at 2am before a deadline.
→ No taste. The code works. It passes tests. But it doesn't reflect any coherent design philosophy.
→ No friction. The thing that used to slow down bad decisions — the effort of actually typing them — is gone.
"Taste" Is the Actual Moat
The pmdata piece argues that the real challenge is encoding engineering taste into these systems. I believe this also hits the mark.
Taste is why a senior engineer's "simple" solution looks different from a junior's "working" solution. It's the difference between code that survives contact with the next feature and code that collapses under it.
AI tools don't have taste; they have patterns. They will output code that seems reasonable but they don't have a belief on how something should be developed. 🧠
And here's the uncomfortable part: most teams can't even articulate their own taste. It lives in code review comments, hallway conversations, and the gut feelings of people who've been burned before. Good luck putting that in a system prompt.
Your Existing Processes Will Break
Code review? Already stressful. Now picture going through the output that comes in such bulk that no human team could even review it.
Refactoring sprints? They inherited debt built up over quarters. Not overnights.
Linting and static analysis catch syntax-level issues. They don't catch "this architecture will be a nightmare in six months." That's a judgment call. That's taste again.
The teams that survive this aren't the ones generating code fastest. They're the ones who figure out how to maintain velocity without drowning in their own output. 🏊
What Actually Helps
I don't think the answer is "stop using AI tools." That ship sailed. That option is no longer available to us.
→ Treat AI output like a pull request from an untrusted contractor. Review it like you'd review code from someone who doesn't know your system.
→ Invest in architectural guardrails before you invest in generation speed. If you can't describe your system's taste in writing, an AI definitely can't follow it.
→ Accept that "fast" and "maintainable" are in tension. Every team needs to decide where they draw that line, deliberately, not by default.
The Real Question
AI technical debt is not a later problem. It is accumulating right now, in every codebase where a generated file was submitted without a close read. The term is coined because the hurt is already there. 💥
We built decades of processes around human-speed mistakes. We have maybe months to adapt them for machine-speed mistakes.
So here's what I want to know: has your team changed any process specifically to handle AI-generated code quality? Or are you still treating it like regular tech debt and hoping for the best?
