How do you give 120+ engineers AI coding agents — and NOT break production? Ryan Cormack, Principal Engineer at Motorway and AWS Community Builder (recognized as a Renaissance Developer by Werner Vogels), shares the exact system his team uses to ship 250% more deployments while keeping quality high. In this episode, we break down the 5 quality gates that let Motorway's engineering teams move faster without sacrificing reliability: spec-driven planning to catch design issues before a single line of code is written, AI-assisted code review to verify code matches the plan, deterministic tests (unit + integration) as an automated safety net at the boundary, cyclomatic complexity checks to keep code maintainable, and human review as the final gate that stays human. Ryan explains how cross-functional DevOps teams — organized like Amazon's two-pizza teams with full end-to-end ownership — enable faster AI adoption. He walks through running parallel agents to explore multiple solutions simultaneously, building custom tools on top of ACP (Agent Client Protocol), and sharing agent configurations across 120+ engineers via a Git + S3 pipeline. The conversation also covers the Renaissance Developer mindset that Werner Vogels introduced at re:Invent 2024: curiosity, ownership, systems thinking, communication, and experimentation. Ryan shares how Motorway embraces this philosophy by encouraging engineers to build their own tools, experiment with new technologies in parallel, and focus engineering time on design and planning rather than writing code. Whether you are scaling AI coding assistants across a large engineering org, building quality gates for agentic development, or rethinking how your team ceremonies and processes should evolve in the age of AI, this episode offers a practitioner's blueprint from someone delivering measurable results: 250% more deployments, 4x engineering throughput, and no uptick in production incidents.

With Ryan Cormack, Principal Engineer at Motorway