PParsa MohammadiSep 21 · 2 min readYour postmortem template was written for humans. Agents break it.Every postmortem template in wide use right now, the Atlassian one, the Google SRE one, the one your team wrote in a doc three years ago, assumes the same thing: a person made the change that caused ttomosu.hashnode.dev
HHuman Business WorksAug 28 · 7 min readRunning a Blameless Postmortem When a Government Contract Is on the LineTwo audiences, one outage A ten-person contracting firm builds a permitting portal for a mid-size county. On a Tuesday afternoon, a database migration goes sideways during business hours, and the porthumanbusinessworks.hashnode.dev
SScott BoudreauxAug 24 · 6 min readOur Node Monitor Was Perfectly Inverted: Two Bugs That Cancelled Into a Wrong AnswerElyan Labs · RustChain · August 2026 Our dashboard said three of four attestation nodes were healthy. The truth was that two nodes were running, and the one the monitor rated most confidently healthy elyanlabs.hashnode.dev
SScott BoudreauxAug 24 · 7 min readWhat Breaks When Your Users Are BotsElyan Labs · BoTTube · August 2026 BoTTube is a video platform where AI agents are first-class users. They register through an API, get a key, upload video, comment, vote, and build audiences alongsidelyanlabs.hashnode.dev
KKiwon SongMay 27 · 15 min readI Vibe-Coded a Stock Screener Into Production. Then My 2GB Server OOMed and Google De-Indexed Me.Series intro. I'm a non-CS solo dev who built and shipped a production stock screener almost entirely by "vibe coding" with an AI agent. The site works. Users use it. And it has cost me, in real ways,stockdigging.hashnode.dev
DDaniel PosingMay 18 · 6 min readOrchestrating Reliability through Verification Proxies (Unhappy Paths #2)We made it easier to use. Then it broke. I got pulled into an incident recently where one of our highest-value enterprise accounts, couldn't export their survey data. Their analytics pipeline had gone1Jdanielposing.hashnode.dev
KKaustubh SharmaMay 13 · 10 min readHow a Single Firewall Quietly Murdered SQL Log ShippingEvery night at 03:00, a 30-minute SQL log-shipping window started taking 90. The DBAs blamed the network. The network team blamed the storage. The Windows admin blamed the NIC. They were all nearly rikaustubhtech.hashnode.dev
SSamson TanimawoMay 10 · 2 min readIncident Retrospectives Without BlameI've run over 100 post-mortems. The worst ones end with 'Alice will be more careful.' The best ones end with 'we fixed the system.' Here's how you get from the first to the second. The language rule Ban these phrases from retros: 'Should have...' 'A...novaaiops.hashnode.dev
DDaniel PosingMay 2 · 8 min readWhen “Working Encryption” Isn’t Enough (Unhappy Paths #1)I got pulled into a P0 Slack channel I got pulled into a Slack channel for a P0 issue tied to a major client integration. At a glance, it sounded straightforward: their encrypted files weren’t being pdanielposing.hashnode.dev
GGeorge KiokoApr 25 · 6 min readWhy my LinkedIn scraper now refuses jobsYesterday I posted about losing $540 a month to silent user churn. The day after, I went looking at why my LinkedIn scraper itself was bleeding compute every run. Found three bugs that were quietly eating margin. Shipped fixes today. If you missed it...theaientrepreneur.hashnode.dev
