The Next Commit Podcast
It’s time to let engineers on the ground share the reality of the AI coding revolution.
It’s time to let engineers on the ground share the reality of the AI coding revolution.
Ian Johnson’s team ships six to eight small tickets per developer each day, but speed is not the most important part of the story.
Ian Johnson: Compose the work. Conduct the flow. Let the agents play.
Agents do more than generate code faster: they change which software-engineering practices are practical to apply.
Agents are already changing how software is specified, implemented, reviewed and verified. Michael Tweed explains how Skyscanner is reshaping its engineering organization around that reality.
Michael Tweed: Agents are transforming the engineer’s role. Leadership must change with it.
Quentin walks through his workflow from design and ticket decomposition through Claude Code, automated analysis, AI code review and human approval.
Kesha Mykhailov explains how that speed is changing development at Fin: technical plans and the conversations behind them are disappearing, while expert reviewers face an unsustainable volume of generated code.
Kesha Mykhailov: When agents move faster than organisations can think
Matt Erman explains why that responsibility is as important as ever. Agents know an enormous range of architectural patterns, but without sufficient constraints they can combine valid ideas into a system that works while becoming progressively harder to maintain.
Matt Erman: Your agent writes the code. You still own the architecture
Shashank Patwardhan, known as Shash, is the Application Security Lead at IFX Payments. Before moving in-house, he worked in technical security consulting across multiple sectors, helping organisations test their defences and develop secure engineering practices.
Shashank Patwardhan: Giving agents freedom without giving away control
Simon Vane, Staff Engineer at M-KOPA, connects code quality with the engineering discipline around it. He describes how established pipelines and quality gates supported faster delivery, why he still asks agents to refactor, and how he adapted test-driven development when he stopped writing most of the code himself.