Why Deleting Twenty Posts Required Creating Twenty Records
I added a member's blog to our community RSS feed, accidentally imported twenty old posts, and discovered that deleting them would cause them to come right back.
I added a member's blog to our community RSS feed, accidentally imported twenty old posts, and discovered that deleting them would cause them to come right back.
AuthorMagic gets a regression safety net, CompanyOS learns to read email, CureCancerMagic grows an AI research brain, and I finally delete a feature that was never shipped.
An email pipeline ordering bug reveals the difference between users and contacts, CureCancerMagic gets a suggestions tracker, and CompanyOS learns to serve more than one company.
CompanyOS: a skills-only system that turns Claude Code into the operating layer for an entire company
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