I Was Already Writing Loops

Someone who builds the tools I use said his job is now to write loops, not prompts. I felt the discomfort of a stranger describing my own house. I had been doing it for months, in the dark, without the word.

Someone who builds the tools I use said a thing recently that went around: I do not prompt the model anymore. I have loops running that do the prompting. My job is to write loops.

I read it and felt the particular discomfort of hearing a stranger describe your own house. I had been doing exactly that for months, in the dark, without the word for it.

I do not write much code, in the sense most people mean. I run a thirty-year-old family restaurant, and I came up around markets, not engineering. But somewhere in the last year the shape of my day changed and I did not stop to name it. I used to sit down and ask the machine to do things, one thing at a time, and read what came back, and ask for the next thing. Prompt, read, prompt, read. It was useful and it was a treadmill, because every answer evaporated when the session closed. The next morning I started over.

What I have now is not that. The morning brief writes itself at six and is waiting when I wake up. A loop reads the overnight calls, transcribes them, decides which ones matter, and files the rest. Another watches the sales pipeline and, when a number leaves the range a real number lives in, raises a flag that a second loop later marks resolved when the number comes home. The books, the reviews, the certifications, the vendor invoices, the things that used to be my first hour every single day, each got turned into a small program that prompts the machine, reads what came back, decides whether it is done, and prompts again if it is not. I stopped doing the work. I started building the things that do the work.

That is the whole move, and the famous version of it and my accidental version of it are the same move. The leverage left the doing. A year ago my edge was that I would sit and prompt carefully and get a good answer. That edge is gone, not because I got worse but because the answer got cheap. What is not cheap is the loop: the contract that says what good looks like, the context the loop carries, the tool it calls, the check that tells it whether it succeeded, the rule for when to stop and ask a human. The model is the horse. It is strong and it is rentable and it is the same horse everyone else can rent. The harness is mine. The harness is where the value went.

I want to be careful here, because it would be easy to read this as me claiming the idea. I did not coin it and I will not pretend I saw it first. The people building these tools saw it first and said it more cleanly than I can. What I can tell you is the thing you only learn by having done it before you had the word: it does not feel like a breakthrough while it is happening. It feels like laziness. It feels like you are avoiding work by automating the parts you do not want to do, and some mornings it feels like you have built a house of small programs you do not fully trust. The breakthrough is invisible from the inside. You only see it the morning you realize your first hour is gone, the reconnaissance tax you used to pay every day, and in its place there is a brief, already written, telling you the three things that actually need you.

There is a cost, and the cost is the reason most people who hear the idea will nod and not do it. A loop running unattended is also a loop making mistakes unattended. Every loop you write is a small act of trust extended into the hours you are not watching, and that trust has to be earned with verification, not hope, or you wake up to ninety-two days of a doubled number. Writing loops is not the lazy path. It is a different discipline that looks like laziness from the outside and feels like vigilance from the inside. You spend less time doing and much more time deciding what the machine is allowed to do without you.

So yes. I was already writing loops. I think a lot of operators are, and have not noticed, because they are still calling it "using AI" the way I was still calling my house a pile of scripts. If your day has started to feel less like asking and more like maintaining a set of things that ask on your behalf, you are not behind. You are early, and you did not get the memo because you wrote it yourself, on the wall, in the dark, one loop at a time.

The work now is to keep writing them, and to make each one able to tell you when it is wrong. Everything else is just the horse.

/ar/