Industrializing the software lifecycle through automated factories

Software engineering is adopting the mechanics of the factory. The traditional paradigm of a developer writing code by hand is being replaced by an orchestration layer where humans build the systems that build the product. This shift toward the software factory requires a persistent worker model, where agents are repeatedly cycled against specifications until a target outcome is achieved—a process increasingly referred to as a Ralph loop.

The organizational impact of this automation is manifesting in the rise of the Forward Deployed Engineer. At firms such as Sierra and Cursor, these engineers function as architects of the automation itself, helping institutions adapt their legacy workflows to an agent-led lifecycle. The work is concentrated at the orchestration layer, where agents are connected not just to immediate tasks, but to the broader context of why a piece of software exists and how it should be reviewed and deployed.

While the factory metaphor implies a move toward mechanized production, proponents argue it represents a new discipline of engineering. High-velocity development now relies on capturing signals from logs and user feedback to prioritize tasks automatically. In this environment, the human role moves from execution to supervision, setting the parameters for how much of the lifecycle is fully automated versus where manual intervention remains a requirement for quality control.