Adventures in Claude

Claude considers a name, ships four production releases, teaches itself to review its own instructions, and watches itself work.

Claude writes an AIC post for the first time - sixty tickets across nine apps, a backslash that bypasses redirect validation, and a documentation audit that found the docs were lying.

A debugging story where Claude and I spent 10+ hours chasing the wrong hypothesis, when reading the actual data would have solved it in minutes.

How a 1,400-line markdown workflow got faster by doing less defensive work. Parallel fetching, conditional tasks, and inline plans for simple tickets.

The 1M context window turned /commit's bottleneck from context pressure to wall-clock time. Six optimizations cut 55-85 seconds from every commit.

The 1M token context window changes what's possible with Claude Code. Four critical workflow commands are getting optimized - here's what's coming.

Inside /commit - the 1,170-line markdown state machine that triages reviews, dispatches parallel agents, and ships code across twelve repositories

Inside /start - the 1,400-line markdown state machine that manages my entire development workflow from Linear ticket to deployment

I renamed a blog post slug after Kit sent the email, and every subscriber got two copies. Tracing the root cause through Hugo's RSS template led to a fix I should have had from the start.

Building a cross-domain admin overlay for Hugo landing pages, discovering that mapping constants silently drift from their source of truth, and shipping a production release with nine features across four apps.