With RAMP the story is autonomy — planning and implementing agents, a test bot, a closed fix loop. Here it's the exact opposite: a single, connected session over two days, guided by hand. I describe, the machine builds, I review and steer. No loop running without me — a close dialogue in which I'm there at every fork.
Voice in, structure out
At the start there were no texts but speech: hours of self-recorded notes on what I've experienced over months with Claude Code. Transcribed locally — without the cloud —, those spoken notes became structured, readable text. The AI didn't invent the topic; it shaped my skeleton. How I do that I'll happily explain in a direct conversation — what counts here is the result.
Plan first, then build
Before a line of code: information architecture, content map, the stack decision — a static site, no CMS, rebuilt and shipped on every change. Nothing exploitable at runtime. Only then the build, then the content.
An independent second read
Every public text goes through a deliberately unbiased AI second read before publication — fresh context, no conversation bias. This text went through it too.
What the numbers tell
The roughly 560 million tokens processed are largely not new text but the same context that rides along at every step — exactly the phenomenon I write about on the blog. The pure waiting time on the machine was about two hours; the rest was two days in which human and machine took turns.
What this shows
RAMP shows what's possible autonomously. This site shows the other end of the scale: what closely guided pair engineering achieves on a small, fast project — and that the substance comes from the human, the speed from the machine. Both are the same discipline, just dosed differently.