{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Screaming in the Cloud","title":"Episode 34: Slack and the Safety Dance of Chaos Engineering","html":"","width":"100%","height":180,"duration":1977,"description":"In the early days, angry nerd corners on the Internet viewed Slack and some of its predecessors as, “Oh, it’s just IRC. Now, you pay someone for it.” Many fell into that trap of wondering about what value such systems offered.The big differentiator? Slack is built as a collaborative business tool.\nToday, we’re talking to Holly Allen, who helped make government software better while  serving as the director of engineering at 18F. Now, she’s a senior engineering manager at Slack, a collaborative chat program where you can do most of your work through a rich platform of integrations. Holly enjoys taking a weird set of skills that make a computer do things and convincing people who know how to make computers do things do things.\nSome of the highlights of the show include:\n\nSafety engineering brings chaos and resilience engineering, incident management, and post-mortem processes together for resiliency and reliability\nSlack strives to move really fast while being in complete control\nSlack is primarily on AWS, but is working on a multi-Cloud strategy because if AWS is down, Slack still needs to work\nSlack has a close relationship with AWS and is a collaborative company; it has immediate access to AWS staff anytime there’s a problem\nSlack uses Terraform and Chef and working to determine if its production workflows in Kubernetes would be worthwhile\nDisasterpiece Theater: Real scenario that might happen and surmise what will happen; don’t cause production issues, but teach Slack employees\nSlack hires collaborative, empathetic people to create a collaborative environment where everyone works together toward a goal \nSlack was firmly in a centralized operations model, but is transforming toward development teams to increase responsibility and service ownership\nSlack doesn’t encourage remote work because it’s not in a position to put in that investment; day-to-day work happens in hallways and between desks\nSlack sees itself as an enterprise software company; an enterprise...","thumbnail_url":"https://img.transistorcdn.com/vgV98ushAFvdAFQSQazvt5GYVniCaXSWIjs5eI3r0gQ/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE0OTQvMTU4Mzg2/OTQ4My1hcnR3b3Jr/LmpwZw.webp","thumbnail_width":300,"thumbnail_height":300}