Dev (depresiya) Ops
summary
Talk discusses developer burnout in ops-heavy environments, describing causes like constant on-call duties and production pressure, and presents strategies to mitigate it such as automation, clearer incident processes, shifting responsibilities, and cultural changes within teams. It names DevOps practices and operational tooling as parts of the approach to reduce stress and improve developer wellbeing.
AI-written summary · about
chapters (10)
- 0:00Depression basics
- 3:21Engineer work problems
- 7:58Cognitive dissonance
- 12:09Business demands solutions
- 17:33Toxic devs and miscommunication
- 21:05Solving via communication
- 26:48Hyper-responsibility effects
- 31:53Firefighting alternatives
- 35:03Solution pitfalls
- 37:32Solving for business
related talks
29mDEVOPS DAYS MTL 2018 - Jason Yee
45mBest DevOps Practices for Developers
05mIgnite: What we’re learning about burnout and how a DevOps culture can help
39mPreventing Developer Burnout
31mDevOps for Java Developers (Or Maybe Against Them?!)
33mContinuous Improvements DevOps and Mental Illness
25mHow to Be an Ops in a Dev Team Without Drowning?
46mDevOps for Java Developers (or maybe against them?!)
