Engineers transition from writing code to designing software factories

Arjun Iyer observes that software engineers are shifting from individual contributors to process engineers, a transition where the primary output is the system itself rather than the code (The New Stack, The New Stack). In this factory model, specialized agents perform individual tasks like research, coding, and testing; this requires engineers to define explicit contracts between these agents, specifying the exact shape and proof required for every handoff. At one company, mandating a doubling of pull request output forced a shift where automated review overtook human review within months, proving that speed gains emerge from systemic design rather than individual effort.

This shift requires moving quality checks into the production flow rather than relying on end-of-line inspection. Sakichi Toyoda’s principle of stopping production immediately when a thread breaks now applies to software, where test agents validate every change as it is made. Humans now intervene only where judgment is required, such as defining security boundaries or ethical calls, while agents handle schema migrations and other repetitive tasks behind hard checks. As Amjad Masad notes, "coding agents change work when non-engineers can build, and Replit now serves 85% of the Fortune 500" (Alex Ponomarev from Thriving In Engineering).

"A spec without acceptance criteria gives the coding agent nothing to aim at, and a change without test evidence gives the release agent nothing to trust." This reality forces teams to codify requirements that previously lived only in human heads, ensuring that every agent-to-agent handoff is verifiable. By focusing on these process-level contracts, engineers prevent the compounding errors that occur when agents loop or agree too easily, effectively managing the software factory they have built.