Being Reasonable about SRE
Talkat SREcon19 Europe/Middle East/Africa · on Wednesday, 2019-10-02· at 14:00· Track 2: The Liffey A·
summary
Companies rename ops to SRE and expect instant magic, but the claim is that without analysis this creates higher expectations for unchanged teams and lots of friction. Unity’s monetization group uses an SRE team for ad-serving and finds the real work is proactive communication and learning dev workflows (example: fixing a brittle circuit‑breaker interaction), not just tooling. Successful transitions require leveling up soft skills, treating internal tooling as a product, and engineers who join the devs to address app‑side reliability.
AI-written summary · about
chapters (6)
- 0:00Introduction to SRE
- 3:04Corporate SRE challenges
- 6:11Pitfalls of adoption
- 9:53The SRE hell phenomenon
- 13:27Strategies for success
- 18:13Q&A and closing
related talks
49mWhat SRE Could Be: Systems Reliability Engineering
13mWhat To Do When SRE is Just a New Job Title?
35mCare and Feeding of SRE
45mClearing the Way for SRE in the Enterprise
25mSRE Guiding Principles & Transformational Framework
18mDeploying Humans at the Edge of SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
38m"Disorganizing" Your SRE Organization