A Week of Claude Code Insights
Claude Code's /insights command analyzed a week of my usage. 1,397 messages, 150 hours of compute, and a brutally honest breakdown of where things go wrong.
Claude Code's /insights command analyzed a week of my usage. 1,397 messages, 150 hours of compute, and a brutally honest breakdown of where things go wrong.
Launching CureCancerMagic, completing the AuthorMagic book publishing pipeline, overhauling demo mode, and discovering that the Apple Studio Display refuses to take HDMI from a Raspberry Pi.
I asked Claude Code to review my own usage patterns over the last two months. The retrospective surfaced eight root causes that each appeared three or more times.
Launched an entire cancer care coordination app, shipped a 24-ticket production release, ran a 10-ticket autonomous chain, and audited email infrastructure across 16 senders.
Does a paid memory API add value when you've already built a custom memory system for Claude Code?
From solo dev diary to invite-only community for retired entrepreneurs and coders building with AI
A production release, CEOS v1.0.0 goes public, Hugo binary puzzles for serverless, and the day I realized partial disaster recovery is worse than no recovery at all.
Sunday: From disaster recovery to pastel unicorns
63 commits across 5 repositories - what a full day of building with Claude Code actually looks like
How Claude Code and I built adventuresinclaude.ai in a single conversation - from brainstorming to live site