Most runbooks are write-only documentation -- written by the engineer who built the system, never read by the on-call engineer who needs it at 3am. Here's how I write runbooks that on-call engineers actually use, the structure that survives the moment, and the maintenance pattern that keeps them current.
Engineering Craft
TypeScript, CI/CD, databases, observability -- the skills that make code production-ready.
