The Next Commit

Sonar

The real stories behind AI driven development, straight from the people building it. Every week, we sit down with developers, engineering leaders, and AI transformation champions who are actually using these tools on the ground. It's a grounded conversation about what's working, what's failing, and what's next. In a moment when every tool claims to be a game changer, this is where builders talk to builders, sharing the patterns, pitfalls, and hard won wisdom that only come from doing the work.

Episodes

  1. 1d ago

    Compose the work. Conduct the flow. Let the agents play.

    Ian Johnson’s team ships six to eight small tickets per developer each day. The real story is the system behind that speed. Ian explains how precise requirements, a truthful project charter, small pull requests and layered verification make coding agents dependable. We discuss comprehension debt, legacy refactoring, the amplification thesis and why the developer’s emerging role is to build the thing that builds the thing. About IanIan Johnson is a staff engineer at Parento and author of Harness Engineering, a practical guide to reliable workflows for non-deterministic agents. His work explores how charters, verification and feedback loops can increase delivery speed without surrendering quality or accountability. In this episode01:14: Introducing Ian and Harness Engineering02:16: Ian’s role at Parento and the book’s origins03:10: From autocomplete to agentic coding04:42: Claude Code, Codex, Pi and parallel agents06:34: Engineering a system for parallel agents08:08: Review agents, checks and human accountability10:01: Keeping changes small enough to review11:01: One Jira card, one pull request12:23: Falsifiable criteria and explicit exclusions13:28: AI-assisted refinement without invented requirements14:48: Decomposing features into releasable work17:01: Shipping six to eight cards per developer daily17:59: Feeding review lessons back into the harness20:20: The charter as an agreement with agents23:17: Agents amplify order and disorder24:55: Structuring and indexing project context26:32: Why inaccurate rules damage output27:58: Truthful rules and living migration plans29:39: Refactoring legacy code with tests and TDD31:58: 100% coverage as a local safety boundary33:10: Why cheap code must still be maintainable35:47: Human oversight and comprehension debt36:57: Resisting cognitive surrender39:33: Pairing a junior, senior and coding agent42:57: Evaluating charter and harness changes45:56: Raising the developer’s abstraction level47:33: Building the thing that builds the thing51:06: Amplification and acceptable reliability53:19: Why a hook beats a ruleKey ideasTickets control what an agent builds; the charter controls how it builds it.Small batches and falsifiable acceptance criteria keep agent work reviewable.Tests, hooks and analysis turn standards into evidence.Agents amplify their environment, but humans retain accountability.People and linksIan Johnson on LinkedInIan Johnson on MediumIan Johnson on DEV CommunityHarness Engineering on LeanpubParento

  • 1 Episode

About

The real stories behind AI driven development, straight from the people building it. Every week, we sit down with developers, engineering leaders, and AI transformation champions who are actually using these tools on the ground. It's a grounded conversation about what's working, what's failing, and what's next. In a moment when every tool claims to be a game changer, this is where builders talk to builders, sharing the patterns, pitfalls, and hard won wisdom that only come from doing the work.

Information

  • Creator
    Sonar
  • Years Active
    2026
  • Episodes
    1
  • Rating
    Clean
  • Copyright
    © 2026 Sonar
  • Show Website
    The Next Commit