Creating a notes repository alongside code repositories enhances project clarity and continuity. It serves as a durable knowledge base for plans, decisions, and team structures, accessible to both human team members and agents. This organized approach minimizes miscommunication and maintains project focus, ensuring everyone stays aligned and informed throughout the development process. Continue reading →

Getting a coding agent productive is less about the prompt and more about whether the machine in front of it can actually build, run, and reach the systems the work depends on. Cursor, Claude, Codex, and the rest are fast when the local world is already honest: dependencies install, the app boots, tests can run,... Continue reading →

The text emphasizes the importance of a structured workflow for coding agents to prevent unintended changes. By introducing a three-step gating process—Ask, Plan, and Confirm—developers can ensure that agents check for ambiguities, outline necessary changes, and obtain explicit approval before implementation. This approach mitigates risks and enhances code quality. Continue reading →

The text discusses challenges faced when using multiple coding agents on a single Git working tree, leading to merge conflicts and lost edits. It emphasizes the need for independent work environments through Git worktrees, which allow each agent to operate in its own directory while sharing an object store. The author details a structured solution... Continue reading →

Brendan O’Leary’s recent article highlights the slow adoption of AI coding tools among engineers, noting a widening gap between early adopters and others. Despite challenges like security concerns and past negative experiences, teams that integrate AI effectively gain significant advantages. Current adoption must be disciplined to avoid creating technical debt while enhancing productivity. Continue reading →