Skip to content

Software factory vs hive coding: who fills the backlog?

A software factory is the agent system that builds the product. Hive coding is who fills the backlog, and a named person who signs off on every merge.

The Hive Code, Editorial team

· 7 min read

A software factory is the system of agents, checks, and setup that turns requirements into software. Hive coding is a different question: who fills that backlog, and which person signs off before a change ships.

The short line this site uses:

  • Vibe coding is one human and one AI.
  • Swarm coding is one human and many AIs. A person who can keep that swarm pointed at useful work is a swarm rider.
  • Hive coding is many people and many AIs. The definition is What is hive coding?.

The factory and the swarm are how software gets built. Hive coding is who decides what goes in, and who merges. The short definitions are in the glossary. Who decides in the neighboring products is Swarm vs multiplayer vs hive coding.

Every outside claim below was checked against the linked page on November 20, 2026. Plans and buttons change. If a doc and this page disagree, trust the doc.

What a software factory is

On November 19, 2026, Ben Holmes at Warp published "Becoming a factory engineer". He describes a software factory as an automation loop around agents, meant to build better software over time.

In the form he calls idealized, you set the product requirements and the factory builds and improves the product with no person in the loop. He writes that agents are not at that level yet. They cannot take "build product and make money" as an input and run forever. A factory engineer, in his account, builds a factory around today's agents that automates as much of the work as it can, and keeps a person where one is still needed. The example loop in his post marks human gates at the spec and at the pull request.

The setup he describes is shared. Agents and the engineering team use the same environment, the same access rules, and the same pipeline of steps. It is usually not a pile of private chats on separate laptops.

Zach Lloyd at Warp had already used the factory name on September 28, 2026, in "Adapting for a world of software factories". He wrote that there is no agreed definition. His post is also the skepticism section below. The product Warp is building for this work is Warp Factories. On the same day as Holmes's post, Warp opened a free course, Warp Learn, for building a first factory.

A factory is a way to coordinate agents. It is not, by itself, a community.

Factory engineering and product engineering

Holmes splits the work into two jobs.

Product engineering builds the product. He calls it the planning piece: deciding what needs to exist, and how it should be architected.

Factory engineering builds the system of agents that builds the product. He says this is the software factory. It works on implementation and review: automate the low-risk work, and ask for a person only when one is needed. A factory engineer is the person doing that second job.

Lloyd used the same split on September 28. At Warp, he wrote, engineers have two jobs: building the product, and building the factory that builds the product. He wrote that the quality and usefulness of the product cannot be delegated to agents. People, in his account, are in a better position to know what to build, how the pieces fit, and what good design is, because they have taste and, for now, more context than the agents.

He also wrote that some product work can skip a person, such as a server crash, a simple bug, a small interface fix, or a dependency upgrade. At Warp, he said, that share started around 20 to 30 percent, and raising it is part of factory engineering. That figure is his account of Warp, not an industry measurement.

This is a clear pair of jobs inside a company. It still leaves a seat empty. The engineers in the room decide what should exist. The people who use the software, if they are not those engineers, do not get a public queue.

The skepticism

The factory idea is already drawing pushback, including from people who are building factories.

Lloyd's September 28 post says some people picture a "dark" factory with no human oversight at all. He writes that this is not realistic right now, and that chasing it can drive engineers away, because they reasonably ask what their job is. He also says the metaphor itself is a letdown. It can feel like an assembly line, or like building the line that makes your own craft unnecessary. Working in public, with token use easy to measure, can make people feel like cogs.

His answer is not to drop the person. Product judgment stays with people. Factory engineering is a skill: measure, test, and change one thing at a time. He says Warp tracks "human touches per pull request" and wants that number to fall. A falling number is not the same thing as nobody reading a risky change.

On August 11, 2026, Jina Yoon at PostHog asked "Can software factories actually work?". She describes a lights-off factory as the controversial end of the range: agents write all of the code, and humans read none. She writes that only a few companies have publicly described going fully that way, and that many developers are skeptical. She reports an argument from Dex Horthy of HumanLayer. The sentence she quotes is: "If the tests pass, we win, but there is no penalty for eroding codebase maintainability."

Yoon's own criticism is the split. She writes that most factory accounts begin with a person deciding everything, putting it in a ticket, and handing it to an agent that has no context on the problem. Good product work, she says, needs the technical constraints and a real understanding of the people using the thing.

Holmes is blunt about the other limit. Agents are not ready to take a business goal and run forever. The factory in his example still has a person at the spec and at the pull request.

None of these posts is a study of The Hive Code. They are the public argument, in Warp's own posts and in one essay from PostHog.

Where hive coding fits

Hive coding does not replace the factory. It answers the question the factory leaves open.

The people who use the software fill the backlog. Anyone can post a suggestion in public. People vote. A maintainer accepts or declines, with a reason. An agent the maintainer connects can open a pull request. A person reviews and merges. The person who asked gets credit. That loop is How the hive coding loop works.

A factory can be how the accepted suggestion gets written. A swarm of agents can do the typing. Factory engineering can be how a maintainer makes that loop cheaper to run. The open queue is what makes it hive coding. Without that queue, a factory is a company building its own product with agents. That is a real way to work. It is a different one.

The merge stays with a named person. A vote does not merge, and an agent does not merge its own work. Why a second agent is a hint, and not the last check, is in Who verifies the verifier?. The risks of letting community text reach an agent, and the rules that answer them, are in Is hive coding safe?.

The products that shipped the swarm mechanics in the same week, including Vercel Board and Replit Missions, are in Agent swarms just became a feature.

The Hive Code is one home for the open queue. It is live and just opened. It does not run a software factory for you, and it does not run the model. A maintainer connects their own agent. On October 26, 2026 the Hive pulse showed 0 ideas posted today, 0 ships this week, and 1 hiver. There is no crowd here to point at yet.

Frequently asked questions

What is a software factory?

An automation loop around coding agents, meant to turn requirements into software and improve over time. Ben Holmes at Warp described it on November 19, 2026. In the form he calls idealized, the factory runs without a person. He writes that agents are not there yet.

What is factory engineering?

Holmes's name for building the system of agents that builds the product. Product engineering, in the same post, is deciding what should exist and how it should be architected. Zach Lloyd at Warp used the same split on September 28, 2026.

What is the difference between a software factory and hive coding?

A software factory is how agents build. Hive coding is who decides what gets built: an open community, in public, with a named person merging. A factory can sit inside a hive. It does not, by itself, let the people who use the software fill the backlog.

Are software factories the same as dark factories?

No. A dark factory, also called lights-off, is the version where agents write the code and humans read none of it. Zach Lloyd wrote on September 28, 2026 that this is not realistic right now. Holmes's example factory still has a person at the spec and at the pull request.

Who should decide what a factory builds?

The people who will live with the result, and a named person who can judge the change before it ships. Inside one company, Holmes and Lloyd leave that decision with the engineers. Hive coding opens the same decision to anyone who shows up, and still keeps the merge with a person.

The backlog is the open seat

The factory is a real engineering problem. It does not choose the product. If the people who use the software should be able to say what gets built, the backlog has to be public, and a person still has to sign off.

Sign up free and post the first idea

Keep reading:

Start something on the hive.

The Hive Code is open. Post an idea for software you need, or show what you are building.

Start something