John Allspaw

@allspaw.bsky.social

Cofounder, @AdaptiveCLabs, “the NTSB of Tech” bringing Resilience Engineering to industry. he/him. Won’t speak on all-male panels, and #blacklivesmatter.

The people behind and part of this community have been a huge influence on my own learning and progression around systems thinking and resilience engineering. I’m glad to see the community organizing itself—and to be a member of it all.

@resilienceinsoftware.org · 2y ago

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

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

Decompensation and Cascading Failures

Consider 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

Does anyone have first-hand experience with using an AI agent that has “participated” in the response to an actual incident in a genuinely diagnostic — or otherwise contextually-specific way?

There are a couple of phrases I genuinely despise. One of them is "...we're at an inflection point..." 1. That's not how inflection points work. 2. Hindsight's a helluva drug, isn't it? 3. Just say you are at a loss to explain some recent surprises. It's honest and not unnecessarily dramatic.

For leaders with expectations about how more productive, efficient, etc. the software engineers in their org will be with AI: 1. How are you handling the "Left-Over Principle" challenges? 2. Also: customer comms about the incidents involving code produced AI? (Seems clear #2 is depends on #1)

Beyond just the language setting ourselves up for failure, "root cause" have deeper issues. For me it triggers anxiety everytime i hear it. @allspaw.bsky.social has articulated it very well the issues here. Recommended material for SRE-201: github.com/readme/guide...

What we talk about when we talk about ‘root cause’

Instead of finding the ‘root cause’ to incidents and issues, @allspaw says it’s more accurate to try and break down what created the ‘perfect storm’:

github.com

In 2015, I attended my first Resilience Engineering Symposium. I felt excited and nervous sharing our domain of software with such accomplished audience. A decade later, I’m part of a fast-growing community of others in software passionate about RE, committed to creating a better future.

@resilienceinsoftware.org · 2y ago

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