174: When Your Software Has a Terrible, Horrible, No Good, Very Bad Day

Working Code

Content provided by Adam Tuttle, Ben Nadel, Carol Hamilton, Tim Cunningham, Adam Tuttle, Ben Nadel, Carol Hamilton, and Tim Cunningham. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Adam Tuttle, Ben Nadel, Carol Hamilton, Tim Cunningham, Adam Tuttle, Ben Nadel, Carol Hamilton, and Tim Cunningham or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://staging.podcastplayer.com/legal.

1y ago 48:34

MP3•Episode home

On today's show, we talk about incidents and outages at work. Incidents are a fact of life. If you depend on a file system or a database or a third party vendor, at some point, something will break and your service will be degraded. Customers freak out (rightly so); and, it becomes a cross-team effort to try and find the problem, fix it, and effectively communicate updates back to your customers. There's no right way to do this. But, one could argue that there are definitely wrong ways to do this.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here.

217 episodes

#Tech #The Working Code Team