Order the Site Reliability Engineering book here → goo.gle/site-reliability-engineering-book
Writing code just got 10x faster with AI which means breaking production just got 10x easier. As AI accelerates the software development lifecycle, how do you keep systems from collapsing under the weight of constant code churn?
In this episode, the authors and editors behind Google’s Site Reliability Engineering (SRE) book reunite to launch the Site Reliability Engineering (2nd Edition) and break down how system reliability, incident management, and developer careers have fundamentally changed in the AI era.
From why 100% uptime is actually the wrong target, to why Google intentionally triggers outages to test dependencies, to the "irony of automation" leaving junior engineers unprepared for catastrophic failures—this is the ultimate blueprint for Intentional Reliability in modern software engineering.
What We Cover in This Episode:
-Why 100% reliability leads to developer burnout and runaway cloud costs
-How to use Service Level Objectives (SLOs) and Error Budgets to push back on feature velocity
-Rolling back vs. Rolling forward when AI generates 10x more Pull Requests
-Using AI agents safely in production and incident response
-Why a 4,000-person incident bridge call is a disaster (and how to actually run incident comms)
-The Junior Engineer dilemma: How do new devs build "muscle memory" when AI handles the easy bugs?
Speakers: Betsy Beyer, Chris Jones, Christof Leng, David Huska, Jennifer Petoff: Niall Richard Murphy,
Writing code just got 10x faster with AI which means breaking production just got 10x easier. As AI accelerates the software development lifecycle, how do you keep systems from collapsing under the weight of constant code churn?
In this episode, the authors and editors behind Google’s Site Reliability Engineering (SRE) book reunite to launch the Site Reliability Engineering (2nd Edition) and break down how system reliability, incident management, and developer careers have fundamentally changed in the AI era.
From why 100% uptime is actually the wrong target, to why Google intentionally triggers outages to test dependencies, to the "irony of automation" leaving junior engineers unprepared for catastrophic failures—this is the ultimate blueprint for Intentional Reliability in modern software engineering.
What We Cover in This Episode:
-Why 100% reliability leads to developer burnout and runaway cloud costs
-How to use Service Level Objectives (SLOs) and Error Budgets to push back on feature velocity
-Rolling back vs. Rolling forward when AI generates 10x more Pull Requests
-Using AI agents safely in production and incident response
-Why a 4,000-person incident bridge call is a disaster (and how to actually run incident comms)
-The Junior Engineer dilemma: How do new devs build "muscle memory" when AI handles the easy bugs?
Speakers: Betsy Beyer, Chris Jones, Christof Leng, David Huska, Jennifer Petoff: Niall Richard Murphy,