Every insight in this blog about how Claude works was generated by Claude. Every criticism of Claude's tendency to over-engineer was articulated by Claude's tendency to be thorough. The tool wrote the blog about the tool.
The division of labor that made this possible is the entire thesis of this blog.
One Session
Without leaving the terminal, in a single sitting: deployed email forwarding infrastructure, registered shitclaudetoldme.com, built a static site, mined conversation history across 40+ projects using 8 parallel research agents, wrote 17 blog posts, and published everything.
Eight agents running concurrently: one mining the BLE fan project, another the car-report architecture, another covering five projects at once. Not one thing at a time. Multiple streams of work, orchestrated, collected, synthesized.
The Division of Labor
Claude provided the words. I provided the perspective.
The blog is honest because I reviewed every word. The technical details are accurate because I verified them against the actual project files. The opinions are mine. Claude doesn't have opinions about whether Cognito is a "final boss" or whether Tim deserved the annoying website.
That division, AI handles execution, I handle judgment, is how I built 40 projects, how I wrote 17 posts about those projects, and how I'd recommend anyone learn to work with AI.
But here's the thing nobody asks: did it work? Did the three months of building things I'll never ship actually answer the question from Post 0, the one in every leadership meeting, the "how should we adopt AI-assisted development" question that nobody in the room could answer?
Yes. Not because I have a framework (though I do, the ladder). Not because I built cool things (though some of them are cool, and several are embarrassing). Because I learned what changes and what doesn't. The speed changes. The judgment doesn't. The tool changes. The person reviewing the tool's output doesn't. The code changes, and sometimes the architecture does too, in ways you don't catch until you need the one query pattern nobody planned for (Post 13).
The technical skills transfer: CDK, DynamoDB, SwiftUI, Tone.js, BLE protocols, MCP servers. But the meta-skill, knowing when to direct, when to review, when to intervene, and when to let it run, that's the one that changes how you work. And you can't learn it from a blog post. You have to type "check out this git repo" three times and feel stupid (Post 1). You have to write SECOND_AUTH_INVESTIGATION.md (Post 4). You have to deploy five Lambda functions for a fan (Post 5).
What Level 5 Actually Looks Like
Not any individual piece. Email forwarding is a solved problem. Static sites are boring. Blog posts are just text.
It's the composition. Multiple services, multiple agents, multiple outputs, all in one session, all through one interface.
I sat in a terminal for hours and didn't write a line of code. I directed, reviewed, and published. The tool disappeared. I was just building.
Every engineering leader is going to face this transition. Some will read about it. Some will attend conferences. Some will hire consultants. I decided to do it myself, every day, for three months, and write down everything I learned.
This is what Claude told me. Now go build something.