Go Get Your Developers Involved
summary
Adopts VictorOps workflows to move code experts into incident response and reports concrete gains: faster deploys, higher availability, and fewer rollbacks, plus measurable code quality improvements when engineers face on-call consequences. Recommends organizational steps—have a clear vision, let teams design rollout, communicate business and peer impact, provide training and a support system—and a three-stage rollout: stage 1: business-hours reachability, stage 2: engineers as escalation, stage 3: route alerts to owning team
AI-written summary · about
chapters (4)
related talks
44mEnhancing the Performance of Engineering Teams
01h 02mDevSecOps for Developers: How To Start
36mDeveloper Experience : From Hype to Reality
32mLessons Learned from 7 Years of Running Developer Platforms
31mSolving Day 2 DevOps Challenges
17mMake Work Not Suck Improving the Developer Experience
25mDevOps Handbook Experiments in Accelerating Delivery
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
