Serverless Craic from The Serverless Edge

Serverless CrAIc Ep84 AI-Generated Code Is a Liability: Technical Debt & Engineering Excellence

Serverless Craic from the Serverless Edge Season 1 Episode 84

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 21:12

Send us Fan Mail

Is AI-generated code creating more value — or more liability?

In this episode of Serverless Craic, David Anderson, Mark McCann, and Michael O’Reilly explore why one of software engineering’s oldest principles is suddenly more relevant than ever in the age of AI:

“Code is a liability. The system is the asset.”

As agentic AI and code generation tools accelerate development, teams are producing more code, more tests, and more complexity than ever before.

But:

Does more code actually mean better outcomes?
Are organisations creating massive technical debt without realising it?
What happens when AI accelerates poor engineering practices?
And how do you maintain confidence, security, and quality in probabilistic systems?

This episode explores:

AI-generated code and technical debt
Validation, verification, and testing strategies
Observability and evaluation frameworks
Security vulnerabilities and unmanaged code
Critical thinking in modern software engineering
Why “lines of code” ≠ business value
The return of XP and foundational engineering principles
Chapters

00:00 – Introduction
00:24 – Old engineering principles returning in the AI era
00:51 – The return of Extreme Programming (XP)
01:43 – “Code is a liability” explained
02:46 – AI-generated code and growing technical debt
03:32 – Why engineers must review AI-generated code carefully
05:16 – The history of generated code and technical debt
06:28 – Why more code doesn’t mean more value
07:12 – AI hype, supply chains, and unmanaged complexity
08:30 – AI accelerates weak engineering practices
09:02 – Why teams still struggle with testing strategies
10:39 – Observability and deploying with confidence
11:54 – Evaluation frameworks for probabilistic systems
12:55 – System boundaries and verification
13:11 – Engineers are still accountable for AI-generated code
13:50 – Critical thinking in probabilistic systems
14:44 – Security vulnerabilities and unmanaged legacy code
16:27 – Commodity systems vs unnecessary custom code
17:25 – AI models finding security vulnerabilities
18:38 – Exploration, testing, and security charters
20:02 – Why code liability matters more than ever
20:24 – Engineering excellence as competitive advantage
20:44 – Final thoughts

Resources & References

📘 Concepts & People Mentioned

Ward Cunningham — Technical Debt
Kent Beck — Extreme Programming (XP)
Dave Farley — Continuous Delivery & modifiable systems
Dan North — Engineering practices & architecture
Elizabeth Hendrickson — “Testing = Checking + Exploring”

📚 Topics Discussed

Technical debt
AI-generated code
Agentic AI workflows
Evaluation frameworks (evals)
Observability
Continuous verification
Security scanning
Probabilistic systems
Platform engineering
Serverless architecture
Engineering excellence

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube