The latest articles on DEV Community by Akhil (@akhil_sharma_28). https://dev.to/akhil_sharma_28 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3890072%2Fd8d4fb4b-b338-4b75-92d4-7f4685ae7d34.png https://dev.to/akhil_sharma_28 en Akhil Tue, 21 Apr 2026 05:04:57 +0000 https://dev.to/akhil_sharma_28/i-got-tired-of-writing-runbooks-after-incidents-so-im-building-something-1e78 https://dev.to/akhil_sharma_28/i-got-tired-of-writing-runbooks-after-incidents-so-im-building-something-1e78 <p>Working on a microservices-based platform, I kept running into the same frustrating cycle:<br> Something breaks → we figure out the fix in real time → someone says "we should document this" → nobody does → same thing breaks 3 months later.<br> Even when runbooks existed, they were either too generic ("restart the pod") or specific to whoever wrote them and completely useless to the next on-call person.<br> So I'm building RunbookAI — you describe your stack once (AKS, EKS, Node.js, PostgreSQL, whatever) and it generates incident playbooks grounded in SRE best practices. Stack-aware, not copy-pasted templates.<br> Very early stage — just launched a waitlist today.<br> My question to the Dev.to community: What's the worst runbook experience you've had? Either nonexistent, outdated, or just completely wrong? Would love to understand the real pain before I build the wrong thing.<br> Waitlist: runbookai.in</p> devops sre productivity beginners