---
title: "Dispatches from O'Reilly: Inside a software factory"
description: "A software engineer with over seven years of experience built a software factory called Squid to ship projects with minimal human intervention, but the first version was overbuilt and abandoned. The article formalizes the software factory as eight stages across three buckets: what to build, actual building and checking, and self-improving, with a shared context layer feeding data into the front of the pipeline. The human is most needed in brainstorming and planning, where taste and high-leverage decisions live, while agents handle grunt work and execution. The author recommends using the strongest model for planning and cheaper models for execution, and warns that a weak plan causes more retries and higher costs. The article advises starting with the smallest loop that automates one annoying part of your job, and buying off-the-shelf solutions when engineers you don’t supervise run agents."
---

# Dispatches from O'Reilly: Inside a software factory

[Stack Overflow](https://yomu.fyi/company/stack-overflow) · Paul Iusztin · Nov 20, 2026

**Type:** Explainer

## Summary

A software engineer with over seven years of experience built a software factory called Squid to ship projects with minimal human intervention, but the first version was overbuilt and abandoned. The article formalizes the software factory as eight stages across three buckets: what to build, actual building and checking, and self-improving, with a shared context layer feeding data into the front of the pipeline. The human is most needed in brainstorming and planning, where taste and high-leverage decisions live, while agents handle grunt work and execution. The author recommends using the strongest model for planning and cheaper models for execution, and warns that a weak plan causes more retries and higher costs. The article advises starting with the smallest loop that automates one annoying part of your job, and buying off-the-shelf solutions when engineers you don’t supervise run agents.

## Context

The author, a software engineer with over seven years of experience before the coding-agent era, built a software factory called Squid to ship Decoding AI’s small and medium projects. The article was written in July 2026 and references the AI Engineer World’s Fair 2026, where software factories were a core theme. The author argues that the industry is overcomplicating concepts like loop engineering and graph engineering, and that the software factory is a more actionable frame for delivering software with autonomy.

## Approach / What changed

The author built a software factory called Squid to ship small and medium projects with minimal human intervention. The factory is structured as eight stages across three buckets: what to build (triage/intake, brainstorming, planning), actual building and checking (implementing, review, review-CI, release), and self-improving (monitor/incident response). A shared context layer, such as an LLM Wiki, feeds data into the front of the pipeline. The author recommends using the strongest model for brainstorming and planning, then cheaper models for execution, and advises starting with the smallest loop that automates one annoying part of the job.

## Takeaways

- A software factory automates the entire SDLC with minimal human input, structured as eight stages: triage, brainstorming, planning, implementing, review, review-CI, release, and monitor/incident response.
- The human is most critical in brainstorming and planning, where taste and high-leverage decisions live; agents handle grunt work and execution.
- Use the strongest model for planning and cheaper models for execution; a weak plan causes more retries and higher total cost, erasing the price gap between model tiers.

## FAQ

### What is a software factory?

The software factory is a framework that automates the entire software development lifecycle with minimal human input. It consists of eight stages: triage/intake, brainstorming, planning, implementing, review, review-CI, release, and monitor/incident response. A shared context layer, such as an LLM Wiki, feeds data into the front of the pipeline, and production signals loop back as new tasks.

### Where does the human belong in a software factory?

The human is most needed in the brainstorming and planning stages. Brainstorming is where taste lives, and the human must understand user data and propose a feature spec. Planning is where the human transforms the spec into an implementation plan, using the agent to scan the codebase and refine the plan. The author notes that the bottleneck stubbornly stays at planning.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [CI/CD](https://yomu.fyi/topic/ci-cd), [LLMs](https://yomu.fyi/topic/llm), [Software Engineering](https://yomu.fyi/topic/software-engineering)

- Source: [Stack Overflow](https://stackoverflow.blog/2026/11/20/dispatches-from-o-reilly-inside-a-software-factory)
- Source URL: https://stackoverflow.blog/2026/11/20/dispatches-from-o-reilly-inside-a-software-factory
- Ingested by Yomu: 2026-11-20T18:00:17.992Z

[Read original post](https://stackoverflow.blog/2026/11/20/dispatches-from-o-reilly-inside-a-software-factory)
