Resilience Coffee/2025/06/20

Introductions Topics: Knowledge graphs—wrestling with resilience engineering knowledgekent beck’s simple diagram, extreme programming explained, first edition, p. 70, end of chapter 11 How could this work.whiteboarding in person is different than remotely with softwarecausal loop diagram—as a group activitycontrast individual knowledge graphs (like in obsidian)shared knowledge graphs as “campfire conversations” and “cave paintings” How adaptive systems fail The 3 modes are: DecompensationWorking at cross purposesGetting stuck in outdated behaviorsCommon Ground and Coordination in Joint Activity examples discussed: convoy from cocktail party to neighborhood, design conversations at a whiteboard, incident response, pilots at takeoff and landing How a Cockpit Remembers Its Speeds the width of the speed bugs were a discovered affordance that was not originally in the design a naval aviator explained how the model that aviation uses for takeoff and landing is wrong… better model is about angle of attack between the wing and the wind.

Doing timezone math to convert to UTC can be much harder than something like “living” in UTC so that it becomes second nature“Why I switched to UTC and never looked back” - https://timestripe.com/magazine/blog/timezone/ We didn’t get to these topics: faced with a terrible idea from a leader: how do you move the conversation toward something healthier, also with humilityBurnout—and recovery Springs, Neaps and Icecream outages https://web.archive.org/web/20070209083903/https://use.perl.org/~godoy/journal/9361https://www.cs.cmu.edu/~wkw/humour/carproblems.txt