5 ways to burnout your engineers
summary
Calls out five explicit anti-patterns and then flips to fixes: hires with 3‑month interview processes and zero onboarding, measures everything in one opaque dashboard and uses those metrics in reviews, migrates VMs to cloud then forces all work through ticketing, shifts everything left until teams juggle many tools and languages, and forbids cross‑team collaboration while expecting unpaid learning and chores. Cites a 50–80% early‑leaver rate and recommends onboarding, measuring business outcomes, treating infrastructure as a product, the DevX framework and the new DevOps/Dev report as remedies.
AI-written summary · about
related talks
05mHow to Destroy a DevOps Engineer
30mHow to build an anti-burnout tech organization
05mIgnite: What we’re learning about burnout and how a DevOps culture can help
29mDEVOPS DAYS MTL 2018 - Jason Yee
21mEliminating Hero Culture on our Engineering Teams
25mBurnout: The Hidden Failure Mode of High-Performing Teams
43mHumane Development
18mWe need to talk about SRE burnout