Skip to content
Sign in
Artwork for Pop Goes the Stack
Pop Goes the Stack · October 13 · 22 min

AI code quality management: Guardrails, hooks, and Open Source

AI is letting teams produce code at a pace we’ve never had to govern before, and “we’ll review it later” doesn’t scale when later arrives after thousands of lines and dozens of commits. In this episode of Pop Goes the Stack, F5's Lori MacVittie, Joel Moses, and Elijah Zupancic tackle the operational problem behind the productivity boom: how enterprises manage AI-generated code quality without turning security and reliability into an afterthought. They make the case that shipping low-quality software has always been a form of malpractice; AI just accelerates it. Elijah introduces the “slow AI” approach: aim for a sustainable 7–15x productivity gain by working iteratively with the model, rather than unleashing fully automated loops that generate massive amounts of code nobody understands. The episode explores practical guardrails, including using hooks in tools like Claude Code and OpenCode to automatically trigger code quality and security checks as files are written, then forcing fixes before the workflow can move forward. They also discuss bringing classic engineering metrics back into the loop, like cyclomatic complexity and maintainability indicators, and using those signals to guide the next revision. A major thread is the open source asymmetry problem. AI-driven code generation and automated bug reports are overwhelming volunteer maintainers, while commercial users benefit disproportionately from the foundations open source provides. The group argues that the industry has to fund and support the critical projects it relies on, especially as AI accelerates both vulnerability discovery and exploit creation. The takeaway: don’t let speed outrun accountability. Build automated validation into your daily workflow, keep humans involved enough to understand what’s being shipped, and invest in the open source “infrastructure layer” your entire stack depends on. Get involved with Elijah's project, Big Code Analysis: https://github.com/dekobon/big-code-analysis

0:00 · Welcome to Pop Goes the Stack-22:25
Play in
Transcript file

transcript

No transcript — this publisher did not publish one.

show notes

AI is letting teams produce code at a pace we’ve never had to govern before, and “we’ll review it later” doesn’t scale when later arrives after thousands of lines and dozens of commits. In this episode of Pop Goes the Stack, F5's Lori MacVittie, Joel Moses, and Elijah Zupancic tackle the operational problem behind the productivity boom: how enterprises manage AI-generated code quality without turning security and reliability into an afterthought.

 

They make the case that shipping low-quality software has always been a form of malpractice; AI just accelerates it. Elijah introduces the “slow AI” approach: aim for a sustainable 7–15x productivity gain by working iteratively with the model, rather than unleashing fully automated loops that generate massive amounts of code nobody understands. The episode explores practical guardrails, including using hooks in tools like Claude Code and OpenCode to automatically trigger code quality and security checks as files are written, then forcing fixes before the workflow can move forward. They also discuss bringing classic engineering metrics back into the loop, like cyclomatic complexity and maintainability indicators, and using those signals to guide the next revision.

 

A major thread is the open source asymmetry problem. AI-driven code generation and automated bug reports are overwhelming volunteer maintainers, while commercial users benefit disproportionately from the foundations open source provides. The group argues that the industry has to fund and support the critical projects it relies on, especially as AI accelerates both vulnerability discovery and exploit creation.

 

The takeaway: don’t let speed outrun accountability. Build automated validation into your daily workflow, keep humans involved enough to understand what’s being shipped, and invest in the open source “infrastructure layer” your entire stack depends on.

Get involved with Elijah's project, Big Code Analysis: https://github.com/dekobon/big-code-analysis

links1

chapters

12 chapters

more episodes

All episodes