SWFT is a source-linked publication about how product teams turn coding agents into dependable software. It follows the companies building these systems, explains the ideas shaping them, and gives readers a practical way to judge what might transfer to their own work.
Who is SWFT for?
The default reader is a product manager at a technology company. They understand customers, products, tradeoffs, and delivery. They should not need to decode an engineering architecture document before they can ask a good question about coding agents.
Engineers and founders are welcome too. SWFT uses the accepted AI engineering terms so readers can join the wider conversation, then translates each term into everyday language and a concrete product decision.
What does SWFT publish?
- Ideas compare the arguments changing software development. That includes Geoffrey Huntley's single outer Ralph loop, Steve Yegge's multi-agent work graph, and the counterarguments about expertise, context, ownership, and maintainability.
- Company cases explain how a named organization moves work from request to reviewed result, which patterns transfer, and what remains unproven.
- Guides answer practical questions about architecture, pilots, evals, quality, economics, human attention, and release.
- References keep definitions, comparisons, and the field map current for people and machines.
What is SWFT's point of view?
There is no single software-factory shape. A company can combine a bounded production line for one class of work, an agent loop inside that line or product, and a durable work graph coordinating several workers. These are composable layers, not a maturity ladder. The layers matter, but so do the task specification, supplied context, tools, permissions, checks, release path, and learning loop around them. Human attention is often the limiting resource. Wider autonomy should follow evidence.
SWFT is interested in the upside and demanding about the evidence. Company accounts remain attributed. Studies keep their scope and limits. SWFT labels its own conclusions. Tokens, code, and pull requests do not substitute for a useful product result.
Start with Three visions of the AI software factory for the field argument. Use What is a software factory? for the working definition and How to build a software factory for a pilot. The rise of software factories is Ben Guo's personal manifesto. The methods page explains how sources and corrections work.
Who writes SWFT?
SWFT Editorial is the institutional byline for the source-led guides, comparisons, references, and company cases. Those pages are AI-drafted from their cited public sources and independently checked by a second AI editorial-review agent (Codex) for source fit, claim boundaries, overlap, and reader utility. The institutional byline does not imply that Ben Guo personally wrote or reviewed them.
The rise of software factories is different: it is Ben Guo's authenticated, author-owned essay. It was first published on Substack and is republished here with its original body, links, date, byline, and sign-off intact. Ben's personal byline is reserved for that imported work.
The publication is editorially independent. Inclusion in the map is not an endorsement, and coverage is not offered in exchange for payment.