// a developer's journal of learning AI-assisted development, one broken project at a time

I'm an engineering and product leader. I manage teams of developers who build real software for real companies. In late 2025, I realized that if I was going to tell my teams to adopt AI-assisted development tools, I needed to actually understand them myself - not from a demo, not from a blog post, not from a vendor pitch. From the terminal.

So I started using Claude Code. Every day. On everything. 40+ projects over 3 months. Each one got 80% awesome, then vibe coded into the weeds, then I moved on - because the point was never the product. The point was what I learned building it.

the agentic ladder

5 Orchestrating Loops Multiple agents, multiple projects. Five words gets you a feature.
4 Managing the Loop The setup IS the work. CLAUDE.md files, conventions, config.
3 On the Loop Delegate phases, review results. "Build the auth system."
2 In the Loop Writing code together. Review every output, fix every mistake.
1 Prompting Claude is a search engine you type full sentences into.

the posts

Jan 2026 "Make it utterly insane"

Comfortable enough to have fun. Art direction instead of technical requirements. Pranks as proof of fluency.