Colette Alexander and Clint Byrum
33 episodes listed below
PRESS PLAY
A podcast about resilience engineering and software. Ever wondered why things on the internet break? Do you work in software and wish that you could have a Dear-Abby-Like call-in show that could answer your deepest questions about how to make your workplace suck less? We're here to help! Write us anonymously at our open question form Email us at: [email protected] Call us and leave a voicemail, or text us at: (401) 592-7574
Based on 6 episodes we listened to · June 2026
A practitioner-facing resilience engineering show about incidents, AI tooling, and the organizational patterns behind engineering judgment.
This is Fine! works best as a show about what happens after clean engineering diagrams meet real operating pressure. In the sampled episodes, resilience engineering and software operations keep widening into human systems work: incident response, root cause analysis, adaptive…
You want incident advice that knows panic laughs at a multi-page runbook.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A grounded look at reliability across company and geography boundaries.
Clint and Colette answer a listener's question about reliability across company, geography, and consultant-client boundaries, and they do it without pretending there is an easy fix.
Incident response as real organizational work, with clear cross org impact.
This episode keeps its focus on incident response and the people who end up carrying it. It asks who really runs the room, why some incidents move more cleanly than others, and what it takes to make that job count.
A practical case for keeping incident learning close to the event.
How long to wait after an incident before holding the retro becomes the central question, and the episode favors moving quickly enough that the value does not drain away with memory.
A practical case for treating incident status as an operational signal, not just a label.
This episode treats incident status as more than admin language. The best stretch is the one that separates being blocked from simply being delayed, since that distinction changes what the rest of the team does next.
A reminder that failure analysis has to look past the incident and at the patterns around it.
The discussion starts with a hockey wrist injury and uses it to ask what actually caused a failure. That frame works because the hosts keep widening the view: root cause analysis, recurring patterns, and the risk of missing system problems stay in play without losing the thread.
A wary, practical conversation about how resilience ideas meet real listeners.
The conversation works best when it stays grounded in the practical problem of explaining resilience engineering to busy, skeptical people in their own language.
A grounded look at how Lund's resilience engineering program moves from theory into practice.
Lund University comes through as a practical place to learn resilience engineering, not just a name on a diploma. What lands best is the program's structure and the in-person labs, which make the time commitment feel concrete.
A loose panel that treats AI coding as a supervision challenge, not a magic trick.
A panel spends most of its time on the practical shape of coding with AI: where LLMs help, where they turn into a supervision problem, and when the better move is to leave them out.
Long-form interviews on AI coding agents, infrastructure, and security, plus a recurring SED News roundup.
Founders and engineers on AI coding agents like Claude Code, and supply chain security.
Stack Overflow's Ryan Donovan interviews founders and engineers on AI agents, protocols, and dev tools.
Michael Kennedy interviews Python maintainers on packaging, security, web tools, and AI.
Michael Kennedy and Brian Okken run down the week's Python tooling, typing, and packaging news.
Matt Stratton interviews DevOps practitioners on security, platform engineering, and trusting AI-written code.
The hosts introduce a special episode featuring John Allspaugh and Dr.
The episode opens in familiar life mode, with weather, kids, skiing, hockey, and the kind of Monday chaos that makes everyone sound a little more human.
The hosts discuss a listener question about calculating the ROI of reliability and resilience work in software, exploring why it's hard to measure, the role of product management, and models like Rasmussen's safety boundaries.
Two software reliability engineers do a deep dive into the academic paper 'Going Solid: A Model of System Dynamics and Consequences for Patient Safety' by Richard Cook and Jens Rasmussen.
Clint and Colette open from a cabin in northern Michigan.
Clint and Colette open with a bit of life turbulence and the familiar sense that the brain only has so much room.
Clint and Colette open with travel banter about Australia and Fiji, including kangaroos, wallabies, and a short detour into the odd force of Australian wildlife.
Clint, Colette, and John Allspaw mark the turn of the year with teasing, holiday logistics, and a fair bit of exasperation about how ready everyone is to leave this year behind.
Clint and Colette start with a San Francisco hotel, a conference, and a 4.3 earthquake.
The hosts open on Thanksgiving-week chaos and the familiar trick of trying to cram five days of work into two.
Clint and Colette start with Halloween, family logistics, and the usual busy life before drifting into incident work.
Clint and Colette open on the time change, and neither of them sounds especially pleased about it.
The conversation starts with holiday weekend banter, kids running around, and a quick nod to what a house sounds like when it is on the verge of becoming childless-ish.
Clint opens on a long ski weekend, fresh powder, and the sun-bronzed aftermath of too many hours outside.
Clint starts with a hockey wrist injury.
The hosts discuss their recent experiences at SRECon, including a spicy talk that sparked an impromptu AMA session.
The hosts discuss fixing a microphone issue and reflect on their troubleshooting process, relating it to incident management in software.
The hosts discuss resilience engineering, on-call experiences, and personal anecdotes about floating tanks.
The hosts discuss personal anecdotes and a metaphor about stretching tape, relating it to their work in resilience engineering.
The hosts discuss a listener question about why SRE leaders in resilience engineering are burnt out and overloaded due to incident-related anti-patterns.
The hosts discuss personal tech mishaps and introduce the show's theme of resilience engineering in software.
The hosts discuss recent incidents and the importance of resilience engineering in software, sharing personal experiences and reflections.
The hosts catch up after the holidays, discussing illness, a canceled trip, and a chicken-related incident.
The hosts introduce their new podcast about resilience engineering in software, inviting listeners to share their work struggles and successes.