resilienceinsoftware.org

resilienceinsoftware.org

@resilienceinsoftware.org

230 followers0 following6 posts

Pinned

resilienceinsoftware.org
@resilienceinsoftware.org

Introducing the Resilience in Software Foundation: a multi-disciplinary group interested in networking with and learning from each other's unique experiences, and helping to disseminate their knowledge to the broader software industry as a whole. resilienceinsoftware.org/news/1092580

resilienceinsoftware.orgIntroducing the Resilience in Software FoundationSoftware failures are inevitable. No matter how hard we try, we can’t make our systems flawless, nor can we predict every possible problem. The systems we’re building today are beyond the mental model...
resilienceinsoftware.org
@resilienceinsoftware.org

You know what? It's time for another older post we had never taken the time to share before! This one's from @spamaps.org, on how you can't build more nines and just add stuff to systems to make them more reliable; there's also a need for the organization to change what it does and how it does it.

resilienceinsoftware.orgYou Can't Build More Nines | Resilience in Software Foundation(Originally published on Medium)Software teams are built to.. well.. build. We have design processes, RFC processes, change management processes.. lots of proce

resilienceinsoftware.org reposted

Fred Hebert
@ferd.ca

Part of Resilience Engineering is knowing Compensation happens, and knowing how to protect, foster, and build on this type of capacity to keep systems successful; keeping it invisible increases the chances it reaches saturation, and fails in a cascade. Posted on @resilienceinsoftware.org

resilienceinsoftware.orgDecompensation and Cascading FailuresConsider the following scenario: A set of automated tasks has somehow failed to run to completion. Because a thorough fix will take some time and the tasks you need run are time-sensitive, you complet...

resilienceinsoftware.org reposted

Fred Hebert
@ferd.ca

I wrote for @resilienceinsoftware.org on "Superficial Blamelessness", where under the label of "blamelessness", we avoid punishing people, yet still focus fixes and interventions based on the same individualistic framing rather than a broader systemic stance. resilienceinsoftware.org/news/11502437

resilienceinsoftware.orgSuperficial BlamelessnessIn 2012, John Allspaw (then CTO of Etsy) wrote a seminal blog post on the need for what he called Blameless Postmortems. Built off the notion of a “Just Culture” from the research of Sidney Dekker, he...
resilienceinsoftware.org
@resilienceinsoftware.org

The words robustness, reliability, and resilience are often used interchangeably, but they are not the same thing. Four members discuss a canonical paper about what distinguishes them, and how to think about moving towards sustained adaptability instead. resilienceinsoftware.org/news/1149720

resilienceinsoftware.orgThree Takes on Four Concepts for Resilience EngineeringEd note: The first time I read Dr. David Woods' paper Four Concepts for Resilience Engineering, I felt so many things click in my brain. While the field of Resilience Engineering is not new, those of ...
resilienceinsoftware.org
@resilienceinsoftware.org

"...if we are serious about wanting to improve reliability, we should be treating our near misses as first-class entities, the way we do with incidents." —@norootcause.surfingcomplexity.com resilienceinsoftware.org/news/1142817

resilienceinsoftware.orgYou're Missing Your Near Misses(Originally posted at Surfing Complexity) FAA data shows 30 near-misses at Reagan Airport – NPR, Jan 30, 2025 The amount of attention an incident gets is proportional to the severity of the incident: ...

You are up to date.