Fear of the Bus: DevOps and Docs
summary
Argues for concrete practices: classify documentation into three categories (critical runbooks, repeatable processes, and secrets) so teams know what to back up and lock down; use lightweight tools like Markdown plus a CMS and variables to publish templates that anyone can fill; enforce a one searchable index so people actually find answers; run regular stock pack days to produce and vet playbooks that survive outages, staff turnover, or S3-style failures.
AI-written summary · about
chapters (5)
related talks
21mLightning Talks - Fear of the Bus: Docs and DevOps
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
20mDo Docs Better: Practical Tips on Delivering...
43m"How To Write Tech Documentation That Will Save Your Career"
38mThe Stuff You Don't Want to Write... Documentation
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
47mThe Things You Don't Want to Write - Documentation
43mThe 7 Deadly Sins of Documentation