Where the software factory came from
Half a century of trying to make software production repeatable. The workers changed; the question did not.
"Software factory" was not coined for AI. It names a recurring ambition: make software production repeatable by standardizing how work is specified, built, checked and reused. The first wave organized people and tools. The second organized models and frameworks. The current wave organizes agents, and it has had to rediscover why the first two cared so much about controls, evidence and feedback.
-
1968
Mass-produced components
At the NATO Software Engineering conference, Doug McIlroy argues that software should be assembled from catalogs of standard, interchangeable components, the industrial idea the factory metaphor grows from.
-
1969
Hitachi Software Works
Hitachi organizes a dedicated software facility, the first of the Japanese "software factories" that would emphasize standardized methods, reusable code, tools and quality control across large programming organizations.
-
1975–1978
The SDC Software Factory
System Development Corporation in the United States names an integrated tools-and-methods effort "The Software Factory," publishes it in IEEE Computer in 1975 and opens a facility in Santa Monica in 1976. It dissolves by 1978 as new projects stop flowing to it.
-
1977–1990s
Toshiba, NEC, Fujitsu
Toshiba's Fuchu software factory and similar efforts at NEC and Fujitsu scale the approach to thousands of developers. Michael Cusumano's 1991 study documents them as a challenge to U.S. software management.
-
2004–2010
Microsoft's Software Factories
Jack Greenfield and Keith Short describe software factories as product lines assembled with patterns, models, frameworks and tools. Microsoft's patterns & practices group ships several factories for .NET.
-
January 2026
The "dark factory" level
Dan Shapiro's five-level model of AI-assisted development names Level 5 the Dark Factory: a black box that turns specifications into software with no human writing or reviewing the code.
-
February 2026
A published operating account
StrongDM publishes field notes on a software factory in which specifications and scenarios drive agents, without humans writing or reviewing the code, validated against behavioral replicas of external services.
-
Today
Autonomy with assurance
The live question is no longer whether agents can write code but what surrounds them: bounded execution, independent gates, a ledger, and authority that is earned per consequence. That is the factory.
What carried over
The 1970s factories learned that standard methods and tools only pay off when work arrives in a predictable shape and quality is measured, not asserted. Model-driven factories in the 2000s learned that generation is the easy part; the product line around it is the hard part. Agentic factories are learning both lessons again with a new kind of worker: the work order replaces the specification document, the gate wall replaces the inspection step, and the ledger replaces the quality report.
The idea that is genuinely new is the dark factory: a factory where routine human writing and review have left the inner loop entirely. Whether that is wise depends on the domain and on the independence of the gates. See who is trying it, and who argues against it.