Increasing the collaboration between SREs and Developers
summary
Most orgs (80–90%) run incidents by best guess; recommendation is to make dev participation mandatory, automate SLO/SLO checks before deploy, and run chaos testing in lower environments not just prod. Harness builds an enterprise workflow that injects SLIs/SLOs into dev pipelines and scores teams with incident readiness scores, seeding hundreds of safe chaos experiments and starting with ~20 (≈20% coverage). Result: faster MTTR, fewer surprises, measurable developer readiness and stronger buy‑in for automated resilience testing.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:48About Harness and reliability
- 2:53Incidents and recovery basics
- 7:28Need for SRE-developer collaboration
- 9:13Current collaboration gaps
- 11:41Reactive vs proactive approaches
- 13:28Proactive practices for collaboration
- 16:43Measuring incident readiness
- 18:51Developer actions for SREs
- 20:13Proactive vs reactive outcomes
- 21:18Chaos engineering benefits
- 22:45Selling chaos engineering internally
- 23:49Naming chaos engineering
- 24:31Starting chaos engineering journey
related talks
25mUnleashing the potential of SRE for modern operations
22mSRE and Risk management: a love story
25mBuilding a highly scalable system to assure Business Resilience
30mHow Did Things Go Right? Learning More from Incidents
42mDemystifying SRE and DevOps
27mGetting Started with SRE
22mSRE for Enterprises
28mHow to Do SRE When You Have No SRE