The Factorio Effect · Dan Grafham

Field Notes · Engineering

The Factorio Effect

Factorio did not predict the AI software factory. It trained the people who would build it, and its mechanics encode the architecture the industry is still fumbling toward. The agent is the item on the belt, not the machine, and that is the trick that dissolves the context problem.

01 · The Game That Was Training

A generation drilled for a job that did not exist yet.

There is already a thing called the Factorio effect. Ask anyone who has lost a weekend to the game and they will tell you it is the compulsion, the just-one-more-belt loop that turns midnight into dawn, the way the factory crawls into your head and starts asking to grow while you are trying to sleep. That is the famous version. It is not the one I mean.

The version I mean is what the game was quietly doing to the people who played it. Factorio is a few hundred hours of training in a single discipline: how to run a system of autonomous producers that you do not personally operate. You do not place the iron on the belt by hand. You build the machine that does, and the machine that feeds that machine, and then you step back and supervise a thing that runs without you. You learn to think in throughput instead of tasks, in bottlenecks instead of effort, in blueprints instead of buildings. You learn that the factory is the unit of work, not the wrench.

That is the exact skill the AI software factory now demands, and almost nobody was taught it on purpose. The people picking up agent orchestration fastest are not the ones with the most LLM theory. They are the ones who already spent a year of evenings learning, in their hands, that you do not do the work, you build the thing that does the work, and then you keep the thing alive. The game was a flight simulator for a cockpit that had not been built yet. Now it has been built, and the simulator hours transfer.

The famous Factorio effect is the addiction. The real one is the training. A generation learned to supervise autonomous production for fun, years before the job existed.

02 · Played, Not Designed

You do not architect a factory. You play through one.

Here is the thing the game teaches that no amount of upfront thinking can replace. You cannot design the right factory from the armchair. You can sketch a plan, and the plan will be wrong, because the problems that matter do not show up on paper. They show up when the belts are running and something backs up two hundred tiles upstream for a reason you could not have predicted until you watched it happen.

So you build a first base. It is spaghetti. Everyone's first base is spaghetti, by law, not by failure. You learn what it teaches you, and then you do the thing that separates the people who get good from the people who stay stuck: you scrap it and start from zero, and the second base is cleaner because the first one taught you where the pain lives. Then you scrap that one too. I am on iteration seven of the real factory. Seven from-scratch rebuilds, each one carrying forward only the lessons, never the structure. That is not a confession. That is the mechanic.

Plan to throw one away · Brooks, The Mythical Man-Month, 1975

"Plan to throw one away; you will, anyhow." The first system you build is the one you learn on. The second is the one that works, because the first showed you the shape of the problem you could not see before you built it. Fifty years before iteration seven, Brooks named the loop and told you to expect it. Factorio just turns it into a save file. The first base is supposed to be torn down. Keeping it out of sentiment is the actual failure, not the teardown.

This is why ground before you theorize is law and not a slogan. In Factorio there is a tech layer you genuinely cannot understand until you have played up to it. Read every wiki page on the late-game and it will still not be real to you, because the constraints of that tier only bite when your factory is large enough to feel them. The real factory is identical. The problems of running a hundred concurrent agents are not visible from the design of running ten. You play through to them, or you do not know them at all.

The first base is spaghetti by law. The right factory is not the one you designed. It is the seventh one, found by scrapping the first six.

03 · The Agent Is on the Belt

The agent is the iron plate, not the assembler.

This is the inversion that makes the metaphor more than a cute parallel, and it is where most people have the picture exactly backwards. The intuition is that the agent is the machine: the assembler standing on the factory floor, the thing that does the work. It is not. In a factory built right, the agent is the thing on the belt. It is the iron plate. It rides in, gets consumed at its station, and is dumped.

The durable machinery is something else entirely. It is the substrate: the dispatch primitive, the chain runner, the supervisors, the belts...