Happy DevOps teams
summary
Advocates creating guilds and regular meetings with everyone’s voice heard, using structured certification for deliberate skill learning, and picking projects that are interesting but not overwhelming; runs consistent retrospectives that surface positives and psychological safety; starts meetings with a live question cube to build connection and hands out kudos so invisible work gets noticed. Recommends blameless postmortems, adopting SRE practices, treating any accessed server as compromised, using infrastructure as code for demos, fixing repeat incidents permanently and running a flock first-line rota to protect focused work.
AI-written summary · about
related talks
42mDemystifying SRE and DevOps
42mDemystifying SRE and DevOps
58mDevOps Counseling: 10 ways to help your Dev and Ops people love each other
15mSustainable Incident Management for happy SRE teams
06mPersonal DevOps
53mGround Truths of a Rugged DevOps Practitioner
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
34mDevops or: How I Learned to Stop Worrying and Love the Ops Team
