Artificial Intelligence1 min read

Dispatches from O'Reilly: Inside a software factory

By · Published by Everything Blog

In short

The operational framework relies on an eight-stage architecture categorized into planning, building, and self-improving operational loops. An intake layer converts research into documented tickets backed by Architecture Decision Record logs before deployment agents begin writing and reviewing code. The workflow also incorporates automated quality assurance and continuous integration fixing agents to streamline delivery. Staging releases require human deployment gates, ensuring engineers retain final authority before software ships.

Key points

  • Modern engineering workflows are actively shifting from traditional manual programming to…: Modern engineering workflows are actively shifting from traditional manual programming to factory engineering paradigms.
  • Autonomous coding pipelines process incoming bugs and feature requests into finished rele…: Autonomous coding pipelines process incoming bugs and feature requests into finished releases with minimal human intervention.
  • Human oversight remains vital at designated deployment gates to ensure engineers retain c…: Human oversight remains vital at designated deployment gates to ensure engineers retain control over high-leverage strategic decisions.

Sources checked by our analysis pipeline: 1

[Ed. note: This article was originally published on O’Reilly Media’s blog, Radar. Republished with permission.]

—————————-

As a software engineer with more than seven years of experience before the coding-agent era, I never liked the idea of vibe coding. But I knew there was a clear line between it and using coding agents to generate clean, maintainable code. That line, where good software principles meet coding agents, is defined by software factories.

That’s why, three months ago, I built my own software factory, Squid, to ship all of Decoding AI’s small and medium projects with minimal human intervention. The first version was so overbuilt I stopped using it.

Meanwhile, I kept seeing people obsess over the next “_____ engineering” label, instead of focusing on actionable outcomes. Prompt engineering, then context engineering, then harness engineering. So far, so good. But in the last few weeks (July 2026 as I write this), things got off track with loop engineering and graph engineering, which already read more like marketing talk than like anything that solves real problems. Graph engineering overtheorizes how teams have…

Artificial Intelligence