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...
Coffee, cookies, and platforms: How to make developers love your platform
DevOps Sauna from Eficode
26 minutes
2 months ago
Coffee, cookies, and platforms: How to make developers love your platform
Send us a text In this episode of DevOps Sauna, Pinja and Stefan talk about what truly makes a developer platform successful—and why forcing adoption never works. They explore the “coffee and cookie principle,” the importance of trust between developers and platform teams, and how to create platforms people actually want to use. Topics include building developer trust, identifying platform ambassadors, balancing freedom and governance, and strengthening collaboration across teams. Whether you...
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...
