Explore every episode of the podcast The Next Commit

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.

Ian 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.

• 01:14: Introducing Ian and Harness Engineering
• 02:16: Ian’s role at Parento and the book’s origins
• 03:10: From autocomplete to agentic coding
• 04:42: Claude Code, Codex, Pi and parallel agents
• 06:34: Engineering a system for parallel agents
• 08:08: Review agents, checks and human accountability
• 10:01: Keeping changes small enough to review
• 11:01: One Jira card, one pull request
• 12:23: Falsifiable criteria and explicit exclusions
• 13:28: AI-assisted refinement without invented requirements
• 14:48: Decomposing features into releasable work
• 17:01: Shipping six to eight cards per developer daily
• 17:59: Feeding review lessons back into the harness
• 20:20: The charter as an agreement with agents
• 23:17: Agents amplify order and disorder
• 24:55: Structuring and indexing project context
• 26:32: Why inaccurate rules damage output
• 27:58: Truthful rules and living migration plans
• 29:39: Refactoring legacy code with tests and TDD
• 31:58: 100% coverage as a local safety boundary
• 33:10: Why cheap code must still be maintainable
• 35:47: Human oversight and comprehension debt
• 36:57: Resisting cognitive surrender
• 39:33: Pairing a junior, senior and coding agent
• 42:57: Evaluating charter and harness changes
• 45:56: Raising the developer’s abstraction level
• 47:33: Building the thing that builds the thing
• 51:06: Amplification and acceptable reliability
• 53:19: Why a hook beats a rule

• Tickets 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.

• Ian Johnson on LinkedIn
• Ian Johnson on Medium
• Ian Johnson on DEV Community
• Harness Engineering on Leanpub
• Parento