The agent writes the code. The team still pairs
Pairing does not become obsolete when an agent implements. Its value moves towards the decisions that shape the code—and sometimes widens into a mob.
Essays and working notes about software architecture, engineering practice, and building systems that can change.
Pairing does not become obsolete when an agent implements. Its value moves towards the decisions that shape the code—and sometimes widens into a mob.
A specification that disappears with the task is a plan. Its lifetime and bounded authority change where product and engineering apply their judgement.
Agents change the economics of producing code. They do not change the need for confidence in changing software.