Guardrails, reviews, and control tradeoffs

AI Coding meets Code Health 🪄 — with Stuart Caborn

Topic 7 of 8

Published Apr 17, 2026 · Clip 47:31–56:38 (9:07)

Stuart explains the guardrail philosophy as DevOps shift-left applied to agents: teach agents that tests pass, coverage is right, and code quality meets team standards before entering CI, avoiding wasted tokens and rework. Today the team is 'trust but verify'—humans still review AI code—but more advanced teams run multiple parallel sessions and are automating review, since 10x productivity can't be gated on human pull-request attention. He stresses observability, low MTTR, and fast rollback as defense in depth, and likens pointless human review gates to change advisory boards that DORA showed slow delivery. Both agree that catching wrong abstractions still needs humans in the loop for now, and that old engineering values—good pipelines, fast recovery—still hold in the AI era.