A friend of mine is dealing with cancer. When I started building CureCancerMagic - a care coordination app for exactly this situation - I noticed something about how information flows during treatment. Doctors send referrals. Friends text you articles. Your cousin emails a link to a specialist in another city. All of it is valuable. Almost all of it gets lost. Sunday I built a feature called the Treasure Trove to fix that, made CompanyOS work for more than one company, and fixed an email pipeline bug that taught me something about the difference between users and contacts in care coordination software. ...

When Anthropic released Claude CoWork , I got excited. A multi-agent system where Claude handles business operations, not just code. I tried it immediately. And I was frustrated almost immediately. The UI was limited. The workflows were rigid. And the biggest problem - it had no overlap with Claude Code. I was already spending my entire day in Claude Code across eight parallel worktrees, building and shipping software. CoWork wanted me to context-switch into a separate web interface to do operations. That’s the wrong direction. I wanted operations to come to me, in the tool I was already using. ...

Claude Code shipped a /insights command recently. I typed it in and waited. A few minutes later I had a full breakdown of my usage over the previous seven days. The numbers: 1,397 messages across 114 sessions. 150 hours of compute time. 91 commits. 435 files touched. 28,509 lines added, 970 removed. I ran 77 parallel session overlaps during the week - moments where multiple Claude Code instances were working simultaneously in different worktrees. 27% of my total messages happened during these overlaps. The multi-worktree setup I built for the Magic Platform monorepo - eight worktrees, each on its own branch - is getting used the way I designed it. ...

Late in the day I plugged a Raspberry Pi 5 into the Apple Studio Display using a micro-HDMI to USB-C cable and got nothing. No splash screen, no error, just a monitor that didn’t react. After some debugging I found the reason: the Studio Display only accepts Thunderbolt 3 video input. It cannot receive HDMI. The USB-C Digital AV Multiport Adapter - the one Apple sells for connecting Macs to HDMI TVs - is a one-way converter. It sends Mac video OUT to HDMI devices. There is no path from a Raspberry Pi’s micro-HDMI output to a Studio Display input. The solution, I thought, was going headless - SSH from the Mac on the same network. But the Pi I bought had all the ports locked down in the configuration, so SSH wasn’t an option either. Amazon is bringing me a 7 Inch IPS LCD Touch Screen Raspberry Pi Monitor Display tomorrow morning. ...

I’m doing 60 days of hyperbaric oxygen chamber therapy and red light therapy to try to address the long Covid thing I’ve been dealing with for a year and a half. I have no idea if it will be helpful, but even if it’s a placebo effect, I’m up for trying. Each day, I have a 30 minute drive to and from the treatment center. So I’ve decided to do two random calls a day. I’m calling people I know but haven’t talked to much recently. These are random - I just think of someone and call them. ...

I was staring at the CureCancerMagic care team invite system when I realized this was the ninth ticket in a row for an app that didn’t exist last week. Care team invites, email ingestion, AI-powered summarization, document management, notifications, reporting, mobile optimization, multi-case support. By the time I shipped the last fix - a migration that almost overwrote PostgREST’s schema list - the app was real. That was maybe a third of the day. ...

I found Supermemory while browsing tool announcements last week. “Universal Memory API for AI apps” - and they have a Claude Code plugin . My first thought was that this solves a real problem. My second thought was that I’ve already built a solution to this problem. So I spent some time figuring out whether Supermemory would add anything to what I already have. Here’s what Supermemory does. When you start a Claude Code session, the plugin fetches relevant memories from their API and injects them into context. While you work, it automatically captures your tool usage - edits, file writes, bash commands, and task spawns - and stores them as structured memories. You get super-search to query past work and super-save to manually flag something important. ...

I’ve been writing Adventures in Claude as a solo dev diary — documenting what it’s like to build real software with Claude Code as your primary collaborator. But the most interesting conversations about this stuff have been happening in DMs, email threads, and random encounters with other people doing the same thing. So I built a community. What It Is Adventures in Claude Community is an invite-only forum for retired entrepreneurs and coders who are actively experimenting with Claude. It runs on self-hosted Discourse on a DigitalOcean droplet, which means you can participate through the web or entirely through email — reply to notification emails to post, or enable mailing list mode to get every message in your inbox. ...

I started the day staring at a pg_roles.rolconfig query result and ended it staring at a Hugo binary size chart. In between - a production release, an open-source launch, and the uncomfortable discovery that last week’s disaster recovery missed 17 files. The morning began with Production Release #182. Forty-one tickets merged from preview to main. The /production workflow I’d rebuilt after the messy February 14 deploy ran cleanly this time - the changelog CLI found its Supabase env vars, the merge sync pattern (git merge -s ours origin/main) prevented the ancestry divergence that bit us last time, and CI passed on first try. ...

Today was one of those days where you look up and realize you’ve been shipping across six different repositories all Sunday. Sixteen commits just to this blog. Thirty-plus across everything else. And somewhere in the middle, a theme called Unicorn got pastel pink cherry blossoms. The Morning: Recovery and Infrastructure The day started with the aftermath of yesterday’s config disaster . While building this site on Valentine’s Day, a symlink command went wrong in one of my worktrees and destroyed the .claude/ configuration directory that all eight worktrees share. The automated backup system I’d built (daily launchd backups with 7-day rotation) saved me - but the recovery was incomplete. Only 2 of 19 files were restored. ...