Attention is all you have
Notes on attention, feedback, and software factories.
As I am building out software factory methodology and tooling, I want to write something that visualizes how human attention remains the bottleneck. There are lots of things we can do to try and avoid issues and direct that human attention the best, but ultimately all that comes down to preserving the product iteration loop as seamlessly as possible. I will publish this piece when I am happy with the animations, which are really the idea I am here to share
Building
Software used to be a fairly literal conversion of attention into product. I looked at one thing, changed it, looked again. The shape got more complete because I kept my attention on it.
Looking back
Then the product started talking back. Data gave me another place to look, so the loop became: product, data, product. The pauses are not accidental. They are the work.
A wider cone
AI gives the machine its own cone of attention. It is wider than mine and can throw off four builds while I inspect one. Great, except the prompt is not the end of the job. I still have to look at what came out.
More things to look at
Now multiply the whole problem: three apps, three data layers, six things that have to make sense together. Before I can give the AI one useful instruction, I have to understand all of them.
The loop runs itself
Ralph loops and heartbeats make the mechanism run without me: read state, build, write the result back, repeat. That is a real factory, or at least a first draft of one. It is also a very efficient way to make the same mistake all night.
See Geoffrey Huntley's Ralph loop and the OpenClaw heartbeat docs.