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 Are password changes really keeping us secure? Is writing passwords in a notebook always bad? Can Apple devices really not get viruses? In this episode of DevOps Sauna, Pinja and Darren take on some of the most common myths around cybersecurity. From password managers, MFA, and VPNs, to cloud security, insider threats, and even the risks of random USB sticks—no misconception is safe. Join us as we separate fact from fiction and uncover how security really works in practice.
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...
