English-language podcasts

Google SRE Prodcast

Ship it! with Vasanth Krishnamoorthy

33 min

Listen through the publisher, then discuss the episode here or arrange an in-person Roundtable. Your city determines where to meet.

Roundtables are designed for groups of four, with a shared subject and room for everyone to speak. Come for discussion, with no dating expectation.

In this episode of the Prodcast, hosts Steve McGhee and Matt Siegler are joined by Vasa Krishnamoorthy, Head of Web Foundations at Pinterest. They discuss what it takes to ship software at scale, how to manage technical migrations, and how AI is transforming the developer workflow. Vasa observes that AI makes generating code faster and cheaper, and it creates new bottlenecks in code review and CI validation, reinforcing that human accountability for trade-offs and quality remains essential.

Episode information is provided by the publisher. Listening takes place on the publisher’s service.

Listen at the source ↗

Featured places to meet in Palo Alto, CA

Explore these places and arrange a conversation through ThinkMatch.

City guide for Palo Alto, CA

More from Google SRE Prodcast

Google SRE Prodcast

Ship it! with the Authors of Site Reliability Engineering, 2nd Edition (Part 2)

43 min

In the second episode of our two-part special, guest host David Blank-Edelman brings core voices behind the Site Reliability Engineering book—Betsy Beyer, Niall Richard Murphy, and David Huska, Jennifer Petoff, and Chris Jones for a discussion on how our understanding of reliability itself has shifted over the past decade. While tooling, error budget formulas, and org charts evolve, the core definition of SRE holds firm: applying disciplined engineering to operations and cultivating a blameless culture of learning. The authors also dig into architectural evolutions like "missing control planes," the necessity of platform engineering ecosystems, and why there is still no "easy button" for SRE. Finally, the group tackles the future of toil in the age of generative AI. Whether you're an aspiring practitioner or a leader looking to articulate the business value of reliability, this episode has wisdom, philosophical debate, and practical advice for navigating the next ten years of productio

Discuss this episode

Google SRE Prodcast

Ship it! with the Authors of Site Reliability Engineering, 2nd Edition (Part 1)

40 min

In this episode of the Prodcast, guest host David Blank-Edelman sits down with four of the editors of the seminal Site Reliability Engineering book—Betsy Beyer, Niall Richard Murphy, Christof Leng, and David Huska—for the first of a two-part retrospective and sneak peek into the upcoming Second Edition (2e). A decade after the original book introduced SRE principles to the world, the team reflects on its runaway success and how the industry has evolved from Google's internal setup to forging independent reliability cultures. The authors share why 2e is a ground-up, complete rewrite—retiring commoditized infrastructure walkthroughs to focus on platform engineering, sociotechnical systems, and real-world case studies from other companies. The conversation also tackles industry dogma around SLOs and error budgets, features a lightning round of the authors' favorite new chapters, and dives into what AI means for the future of SRE. Join us for an honest, funny, and insightful conversation o

Discuss this episode

Community Poll

Public-health protections can justify some limits on individual choice.

Share your view, then see how readers voted. No sign-in required. This poll is shared across stories.

Do you agree or disagree?

Choose one answer

Common Quandary

A Common Quandary to discuss

Another conversation to explore, separate from this news story.

A private joke from years ago goes public. How long should it follow the person who wrote it?

Someone shares a screenshot of a tasteless joke made years ago in a private friends' chat. The person who wrote it says they were performing for a small audience, have changed, and never agreed to have the message made public.

How private should speech remain when it reveals something troubling?

Explore this quandary