Low-Context DevOps: Helping DevOps find answers faster
summary
Claims that high‑context team pain (new hires and oncall engineers stuck without instructions) resolves when documentation is made low‑context: incremental, continuously maintained, and just‑in‑time. Implements three concrete levers: carefully constructed defaults (CI/CD and base libraries that embed operational best practices), make right easy (templates and defaults so the lazy path is correct), and ubiquitous URLs and service‑doc templates — examples include alert templates and a release doc that lets a colleague complete a ship alone.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:45High Context Cultures
- 5:21Low Context Cultures
- 8:49New Employee Environment
- 11:10Make Right Easy
- 16:19Create a culture of documentation
- 19:58Why people avoid writing documentation
- 22:09Blank Screen Syndrome
- 23:03Really Awesome Templates
- 23:51Write in small batches!
- 24:52Where do engineers already write?
related talks
33mLow Context DevOps: Improving SRE Team Culture through Defaults, Documentation
45mThe DevOps Revolution: We Haven't Always Known Everything
09mexplains DevOps Culture
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
28mDevOPs Lessons for Frontend Developers
44mDevops - What does devops culture mean for engineers?
38mKill DevOps
16mDevOps - Philosophy vs Practice