Safe Landings: Self-care In A High Intensity Technological World
summary
Conference data shows 43% feel disengaged and 51% feel they're underperforming then connects those stats to concrete fixes: deploy relevant monitoring and proactive alerts, keep runbooks and a postmortem log (the 3:00 a.m. rule), practice failures in a non‑prod cloud sandbox, define escalation points, and cross-train the team. A real incident—an express route outage between cloud and on‑prem—proves breathing, standing up, headsets and documentation speed diagnosis and reduce burnout.
AI-written summary · about
chapters (12)
- 0:00Self-care in tech
- 3:58Focus on self-care
- 7:28Monitoring tools in high-pressure roles
- 13:05Reduce stress in operations
- 19:303 a.m. rule for incidents
- 23:45Prevent burnout
- 27:57Calming techniques
- 33:42Issue responsibility
- 38:43Failure perspective
- 41:10Advocate for tools
- 44:38Myth of rockstar engineer
- 47:09Balance work and well-being
related talks
31mDon't Forget the Humans
42mHidden Hazards: Unique Burnout Risks in Tech
28mBuilding a healthy on-call culture
29mDEVOPS DAYS MTL 2018 - Jason Yee
18mWe need to talk about SRE burnout
54mService degraded: Tackling burnout in the IT industry
44mNine-to-Five and then F*ck It - Maintaining Psychological Safety in Technology
33mIt's Dangerous To Go Alone! Take This Team