Low Context DevOps: Improving SRE Team Culture through Defaults, Documentation
summary
Argues SRE teams must be carefully constructed defaults, make right easy, and ubiquitous documentation so newcomers and on-call responders aren't blocked. Gives concrete fixes: provision workstations, software, and access faster; use a forked OpenSSL-style library with a “timelessly correct” API so secure defaults are automatic; embed deep-linked docs in alerts, CI/CD and error messages; adopt short templates and small-batch edits (service docs, alert runbooks) and treat doc bugs like code bugs so the approach actually scales.
AI-written summary · about
chapters (8)
- 0:00Introduction to low context
- 2:42High vs low context culture
- 5:57Defining low context DevOps
- 10:06Carefully constructed defaults
- 12:34Making the right path easy
- 16:08Ubiquitous documentation
- 22:14Overcoming documentation hurdles
- 29:34Leadership and conclusion
related talks
30mLow-Context DevOps: Helping DevOps find answers faster
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
20mDo Docs Better: Practical Tips on Delivering...
45mThe DevOps Revolution: We Haven't Always Known Everything
29mFear of the Bus: DevOps and Docs
01h 02mDevSecOps for Developers: How To Start
42mDeploying SRE Training Best Practices to Production: How We SRE'ed Our SRE Education Program
32mTales from the DevOps Transformation Trenches