The latest articles on DEV Community by darthmortem (@darthmortem). https://dev.to/darthmortem https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4144692%2F150661a1-8e24-4132-ae59-4af58a7f133c.png https://dev.to/darthmortem en darthmortem Sat, 26 Sep 2026 18:06:45 +0000 https://dev.to/darthmortem/darthmortem-paste-your-slack-chaos-get-a-postmortem-draft-in-60s-223m https://dev.to/darthmortem/darthmortem-paste-your-slack-chaos-get-a-postmortem-draft-in-60s-223m <p>The worst part of an outage isn't the fix. It's the hour of report-writing afterwards when you're already exhausted.</p> <p>So I built <a href="https://muse.ai/s/postmortem-drafter-wv6arihw91xu" rel="noopener noreferrer">Darthmortem</a> — paste your raw timeline (Slack messages, logs, notes) and get a structured postmortem draft: summary, timeline table, 3 root-cause hypotheses, impact, action items. As markdown you can drop straight into Notion/Confluence.</p> <p>Why I built it this way:</p> <ul> <li> <strong>No signup, no backend</strong> — runs entirely in your browser. Nothing uploaded. I don't want your incident data either.</li> <li>Handles both <code>14:02 - event</code> and <code>14:02 | event | source</code> formats</li> <li>Auto-calculates <strong>detection gap</strong> (impact → detection) — usually the most useful number nobody bothers with</li> </ul> <p>It's free. Try it with your last incident (or a sanitized timeline) and tell me:</p> <p><strong>What's missing from the draft that your team actually needs in a postmortem?</strong></p> <p>Roast me. I want to make this actually useful.</p> showdev sre devops tooling