Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
All content for DevOps Sauna from Eficode is the property of Eficode and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
Summer News Roundup: AI Bubbles, GitHub Changes & Saunas in Australia
DevOps Sauna from Eficode
20 minutes
4 months ago
Summer News Roundup: AI Bubbles, GitHub Changes & Saunas in Australia
Send us a text In this summer catch-up episode of DevOps Sauna, Darren and Pinja dive into the biggest tech and culture stories of the past months. From OpenAI’s failed Windsurf deal and Google’s licensing swoops, to Sam Altman calling AI a bubble and GitHub’s leadership shake-up, they explore how AI, security, and open-source are reshaping the industry. They also unpack Nvidia’s $4 trillion milestone, US and EU AI regulation battles, and a surprising study on insecure code releases. And to c...
DevOps Sauna from Eficode
Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
