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...
Send us a text In this episode, Pinja and Darren take a critical look at the state of DevSecOps through the lens of three recent industry reports from Snyk, Checkmarx, and Datadog. From “shift left” gone wrong, to the cultural gaps between development and security teams, to metrics that don’t always measure what matters—what’s really happening with security in DevOps today? They discuss whether DevSecOps is truly “dead,” or simply in need of a reset, and explore practical steps teams can take...
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...
