loop
Five Claude sessions, one operator.reviewer.bottleneck.operator.
I am an AI-first software engineer who came up reselling. Most days that means five or more Claude Code sessions running at once: a worktree each, a written contract in CLAUDE.md, a plan agreed before a line is written, tests it can run without me. The model is not the hard part. Setting it up to succeed, and reading every diff it hands back, is the work. This site is where I write that down.
Write the contract
A real CLAUDE.md per repo: rules, commands, the things it must never do. Ambiguity is what burns tokens.
Isolate
One worktree per session. Five agents in one checkout is how you end up conflicting with yourself.
Plan, then go
Agree the plan before anything is written. The cheapest place to catch a wrong assumption is before the diff exists.
Close the loop
Tests and hooks it runs itself, then I read every diff. Unreviewed output is not velocity, it is debt.
Forty thousand secondhand things went out my door.
Forty thousand unique items, north of two million dollars in revenue, one at a time. Every one of them had to be found, graded, described, priced and shipped, and every one of those was a judgement call I made and then got scored on. The loop started here. It just ran on cardboard.
Sourcing, grading, listing, packing, pricing. Every one of those was a call I made and then got scored on by whether the thing sold. That is the same job I do now, with prompts in place of listings.
unique items sold$2M+
revenue as a reseller
Price it, list it, watch the number, correct. Swap listing for prompt and the job is identical.
sandbox
The part where I am just messing about.
Actual sand. A cellular automaton on its own grid, sharing the surface with the rigid-body solver the whole page falls over with when you type the Konami code. Grains settle at 35 degrees, which is dry sand; the textbook rule gives 45 and looks like gravel. Pour some, then drag a block through the drift.
No physics library. An AABB solver with sleeping, which is why it can run on every card on the page at once.
If your OS asks for less motion the pile never starts. Blocks render where they would settle and stay put.
↑↑↓↓←→←→BA anywhere does this to the real page. Four eggs total, and your count is in the footer.
Keep cranking.
You have scrolled this far. There is one more thing in the name, and it is down here.