· 4 min read · By Mehul Prajapati
I Run a Software Factory. I Did Not Build It.
511 pull requests merged on one client project since September. I did not build the setup. This is what I do, and how I talk to it.
Claude Code does the building. I keep the yes. That is my whole software factory.
Addy Osmani wrote a good post on this, Software Factories, Light and Dark. Dark means nobody reads what the agents ship. Light means a human stays where a wrong call is costly. Mine is a light one. It has review agents, checks before production and a log of 340 mistakes. Claude Code made all of it. Most of the tech inside is unknown to me.
From 11 September till today that is 245 sessions and about 2,000 messages from my side. Almost half of them are five words or less.
What I type most
- PROD-WRITE-OK, 62 times. Nothing changes in production before I type this.
- "send it", 49 times. Claude Code writes the mail to the client. I read the draft. It goes only after I say so.
- "done" or "continue", 49 times. When it is waiting for me.
- "where are we", 27 times. It tells me what is finished and what is pending.
- I stopped it in the middle, 99 times. When it was going in a wrong direction.
Other than this, I point it to a blog or a GitHub repo and say do this for us. I ask Codex to check what Claude wrote. I rename every session, so I know which one is doing what. I use Remote Control to check from my phone. And I keep caffeinate running, so the laptop never sleeps.
How I talk to it
I did not plan a factory. I was only irritated with the mistakes. This is what worked in the conversation.
1. Don't only fix the mistake. Ask how it happened.
After a mistake I ask four things. What mistake did you log for this? How did it happen? How did the reviewer miss it? How will it not be missed from now on? The last one matters most.
2. Ask for a second pair of eyes.
On 15 September I asked for one review agent that looks at the work like a third person, before anything is called complete. Claude Code made it the next day. It is told to assume there is a mistake and find it.
3. Logging a mistake is not the solution.
By 25 September the log had 128 mistakes and the same ones kept coming. So I said logging is not enough, change the setup so it cannot repeat. Next day it added the first automatic checks. For example, if an agent writes a number that no command produced, it gets flagged.
4. Say go and see how others do it.
I don't know the answer myself. So I say go on GitHub, find how people solve this, compare with us and suggest the improvement. On 23 October it added three reviewer agents plus Codex for every pull request.
5. Keep the yes with you.
It can write the code and the mail. But production and the client wait for my word.
6. Stop it early.
When it goes in a wrong direction I stop it in the middle and say what I want in one line. Short is fine.
The rule behind all six: give the agent only as much freedom as you can check. Addy calls this back pressure.
Did it help?
| Month | Mistakes in the log | Reached a sent mail or production |
|---|---|---|
| September | 169 | 40 |
| October | 118 | 22 |
| November, till the 17th | 53 | 2 |
Claude Code did not stop making mistakes. In November it is still about three a day. What changed is where they stop. The reviewer agent caught 101 of the 340. I caught 35.
Three I still remember
1. It said blocked when it was not blocked.
Twice in three days it told me the task is waiting on the client. Both times we already had the access. Now it has to try from our side two times, in two different ways, before it can say blocked.
2. It built tools instead of doing the task.
One day nine hours went into cloud tooling. The client's fixes were finished and just waiting. Now the task goes first. Tooling comes only after the work is delivered.
3. A night run sat idle for about 8 hours.
I left it running overnight. Everything waited for one step, even the work that did not need that step. Now each piece of work starts when its own inputs are ready.
Is it a real software factory?
90% yes. Only one thing is missing. It does not start work by itself. Today the client's mail comes, I open a session and say check it. It just needs a cron job that takes the task and pings me on my phone. After that Claude Code already does the work, and I say yes or no.
Addy has one line I liked. The person never left the factory, they moved. That is me. I moved from writing the code to guarding the gate.