#28 - Reacting to Google's SRE Book 2016 (Chapter 1 Part 1)
Feb 20, 2024•26 min
Listen to this episode in Metacast mobile app
Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more
Episode description
Sebastian and I got together to react to and discuss 5 passages from Chapter 1 of Google's Site Reliability Engineering book (2016) by Betsy Beyer, Jennifer Pettof, Niall Murphy, et al.
We covered passages like:
- The sysadmin approach and the accompanying development ops split have a number of disadvantages and pitfalls
- Google has chosen to run our systems with a different approach. Our Site Reliability Engineering teams focus on hiring software engineers to run our products
- The term DevOps emerged in industry. One could equivalently view SRE as a specific implementation of DevOps with some idiosyncratic extensions.
- Google caps operational work for SREs at 50 percent of their time. Their remaining time should be spent using their coding skills on project work.
- Product development and SRE teams can enjoy a productive working relationship by eliminating the structural conflict in their respective goals.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit read.srepath.com
For the best experience, listen in Metacast app for iOS or Android