Development
A per-blog toggle, and when not to "fix" a bug
A boolean threaded through four layers, and three independent review passes agreeing on a finding I deliberately didn't fix - because the cache is the dedup mechanism.
Dev log
blog-manager
Development
The blog that couldn't publish on a schedule
A batch pipeline design that started with a five-minute substrate check: future-dated posts weren't hidden, they were 404s, and nothing ever rebuilt the site.
Development
Debugging a hidden checkbox on Medium's real UI
A zero-sized invisible input behind a styled toggle, a disabled state that silently eats clicks, and verification against the live page instead of my own logs.
Development
Adding a Listmonk newsletter integration to blog-manager
A batch is not a 1:1 sync: why the newsletter got its own model, Listmonk's not-quite-Basic auth, a tunnel-gated hostname detour, and a Brakeman provenance quirk.
Development
The runbook that lied twice
A one-line docs fix that turned into three meanings of one hostname, a renamed runner directory, and automation that had reintroduced the exact bug it existed to prevent.
Development
Medium kept dropping my hero image, so the bridge now pastes it in
Two theories disproved at one manual import each, a paste that saved dimensions but no src, and the native file-chooser path that finally attached the image.
Development
Backfilling reality into a syndication tracker
Prod said zero Medium posts; the rake tasks fixed that in minutes. Then the reconciler crashed everywhere, a dashboard got scraped from the DOM, and CI failed three ways.
Development
The syndication tracker that couldn't answer its own question
Absence encoded as missing pills, dead ends in the publish flow, a system test that would have merged silently red, and firewall rules that ate every outbound container packet.
Development
Reconciling Medium cross-posts blog-manager never staged
An RSS feed that silently caps at 10 items, a synthetic-key backfill with an upgrade-only precedence rule, and 76 of 78 titles matching without any fuzzy logic.
Development
Proving the backup actually works
"We have backups" and "we have backups that work" are different claims. A file-level restore, a query against the restored data, and a stray copy cleaned up along the way.
Page 1 of 5