liveBook · Manning

Software factory

As explained in Vibe Engineering

A software factory is an autonomous software-production system in which agents execute the end-to-end code lifecycle while people operate and maintain the system.

A software factory is an autonomous production system in which agents handle the code lifecycle from requirement decomposition through implementation, testing, and deployment. People design, operate, and maintain the factory rather than writing every change, reviewing every diff, or supervising each terminal session. section 5.7

The appealing shortcut is to describe a feature and return to merged code. The practical reality remains less mature: most teams use agentic IDEs or terminal agents, while headless pipelines and multi-agent orchestration introduce approval, coordination, and safety risks. section 5.7

Operating a software factory shifts engineering leverage toward the system around code:

  • Define precise task descriptions and targets instead of manually implementing every task. section 10.8.2
  • Design verification that keeps generated changes honest, including tests, output review, and edge-case handling. section 5.7 section 10.8.2
  • Treat orchestration, permissions, thresholds, and infrastructure as first-class engineering work rather than assuming agents coordinate safely by themselves. section 5.7 section 10.8.2

The dark-factory tradeoff

StrongDM's three-person AI team proposed that humans should neither write nor review code, with a target of at least $1,000 in daily token spending per human engineer. The logic treats agent generation and validation as cheaper than human review, but the economics require a product able to carry roughly $20,000 per engineer per month in inference costs. section 9.1.3

How Vibe Engineering covers it

How deep it goes
Defines the end-to-end lifecycle and human role, then contrasts emerging orchestration with current agentic workflows without specifying implementation internals.
Examples
Uses current agent fleets, StrongDM's dark-factory charter, token spending, task descriptions, and verification infrastructure as concrete examples.
What it assumes
Assumes familiarity with agentic development and code lifecycle stages while distinguishing autocomplete, terminal agents, pipelines, and fleets.
What you can do after
Operate/configure an agent-production system by defining tasks, designing verification, and maintaining orchestration and infrastructure.
How it connects
Connects software factories to agentic IDEs, headless pipelines, orchestration, testing, deployment, verification, and technical leadership.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.