This is Fine! A podcast about resilience engineering and software

The VOID⁠ is one of our favorite things!Some of Courtney’s inoculation of the MTTR virus can be found here:⁠An interview with InfoQ⁠⁠A talk at SRE Con Americas in 2022⁠Courtney’s ⁠recent talk on Automation and AI⁠David Graeber’s Bullshit Jobs started as ⁠a talk⁠ and then a ⁠great book⁠Want to read more about HABA-MABA and CSE/RE? Lisanne Bainbridge’s ⁠The Ironies of Automation⁠ is a perennial recommendation in our show notes⁠The thread⁠ Courtney mentioned from Gergely Orosz

Steve is the host of the Google SRE Prodcast, you should check it out!Colette got her chickens from Greenfire Farms, and her chicken coop from Carolina Coops, if anyone is wondering.The Chris Hayes podcast Colette mentioned about unconditional cash transfers is here.Iain M. Banks is an author of The Culture series, a set of fiction books based in a post-scarcity societyIf you didn’t get the Vizzini/Inigo Montoya references, you should probably find a way to see The Princess Bride.Colette mentioned STAMP - which is more along the lines of reliability engineering than resilience engineering, technically, but is related. You can read about how Google is using it here.Lord, you want the history of ITIL? Okay.**** note, none of the below sponsor us (yet), so these are pure-hearted endorsements from Clint during the episode ****Adaptive Capacity Labs will teach your teams how to be more resilient.Incident.io is who Clint mentioned as one of the many incident automation tools out there (Rootly and FireHydrant are a couple others).Backstage is an open source Spotify product, and anyone who’s worked at Spotify will talk your ear off about how great it is if you let us.*************************A new Resilience Engineering community that Colette and Clint are a part of has launched! You can find us at resilienceinsoftware.org and join to be a part of the conversation in SlackAnd of course, you can email us at thisisfine.softwarepodcast@gmail.com or write to us via http://thisisfinepod.com 

Dive into the intriguing world of resilience engineering, where insights from skiing mishaps lead to a discussion on complex system failures. Explore the evolution from Safety One to Safety Two, emphasizing learning cultures and practical safety measures. The hosts critique resource challenges in the field, advocating for concise guides over vague narratives. They also tackle the pitfalls of unrealistic safety expectations, using real-world examples like the Exxon Valdez spill to highlight the gaps between planning and reality.

Fred Hebert, Staff SRE at Honeycomb.io and technical author, brings a wealth of knowledge in resilience and distributed systems. He discusses the impact of the DORA report on software engineering and workplace culture. The conversation delves into the nuances of burnout, emphasizing self-care amidst rapid technological change. They analyze the complexities of AI adoption in the workplace, highlighting trust issues and leadership styles that can enhance employee well-being. Fred also critiques how corporate interests can skew data interpretation in assessing productivity metrics.

Vanessa Huerta Granda, a technology manager passionate about resilience engineering, shares her insights on navigating metrics in incident management. She discusses the challenges of code freezes and the importance of adaptable metrics. Vanessa emphasizes the significance of context when analyzing Mean Time to Recovery (MTTR) and how it can lead to meaningful insights. The conversation also highlights the necessity for better communication between tech teams and executives to ensure effective decision-making based on accurate data.

John Allspaw, a pioneer in resilience engineering known for his impactful work at Etsy and in the DevOps movement, dives into crucial discussions about safety in software. He addresses how traditional safety concepts clash with software development realities. The conversation highlights the necessity of psychological safety for innovation and explores narrative control's role in software perception. They also examine the dynamics of change management in development, including the risks associated with code freezes and fostering open communication during deployments.

In this engaging discussion, the hosts dive into the world of resilience engineering, sharing personal anecdotes that highlight its significance. They tackle the complexities of maintaining uptime and the common misconceptions surrounding it. The conversation turns to navigating job loss, where the importance of empathy and communication shines through during crises. There's also a call for community involvement, inviting listeners to join the conversation and share their experiences in fostering resilience in the workplace.