One Agent, One Worktree: Isolation and Concurrency for Coding AgentsThree coding agents start from the same checkout and finish in the filesystem they happen to inherit. Parallel coding is not primarily a coordination problem. It is first an isolation problem.5 min read·pragmaticstack.in38JEKSep 24
Tests Are the Verification Layer: Proving Agent Generated ChangesThe coding agent reports that the feature is complete. The project compiles. Four tests pass. The fifth was deleted because it represented legacy behavior. This is one way to achieve a green build.5 min read·pragmaticstack.in24BPSep 22
Reviewing Code Nobody Typed: Human Judgment in an Agentic WorkflowA pull request arrives with thirty seven changed files, polished comments, and a description that explains the architecture with unusual confidence. The reviewer approves it. Two days later the team finds the bypassed authorization rule. Nothing looked careless. That was part of the problem.5 min read·pragmaticstack.in44IISep 17
The Pull Request Is the Product: A Delivery System for Coding AgentsWithin a month there are several teams, several tools, several permission models, and several definitions of done. Management asks how much faster engineering has become. Nobody can say, but the token dashboard is exceptionally detailed.5 min read·pragmaticstack.inSep 15
The Ticket Is the Contract: Specifying Work for Coding AgentsThe team called this agent unpredictability. The ticket was six words long.5 min read·pragmaticstack.inAug 27