Fear and Loathing in Systems Administration
summary
Argues that operations pain is social not technical and prescribes concrete fixes: stop hoarding access, adopt pull requests for config, centralize logs with ELK or spunk and give teams the dashboard URL, add developers to oncall so the obvious 5:1 developer to systems ratio pressure eases, build small automation incrementally, replace shell log grabs and “terminal as a service” with a button via Windex, and measure outages and toil in money and time to make staffing requests credible.
AI-written summary · about
chapters (4)
related talks
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
05mOut of the Basement...
24mOperationalizing Observability: The Invisible Parts
33mDevops' Seven Deadly Diseases
33mOperations: the last Mile for DevOps
21mLightning Talks - Fear of the Bus: Docs and DevOps
41mLessons from Mission-Critical Systems in Fast-Moving Industries
