Two Emails, One Blog Post, and the RSS GUID Problem
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.
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.
I moved every Magic Platform app behind subdomains, gave them all Hugo landing pages, and discovered that our AI development workflow independently invented 85% of a methodology someone else just formalized.
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.
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.
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.
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.