New pages

16:0716:07, 21 August 2026 Resilience Coffee/2026/08/21 (hist | edit) [1,532 bytes] Kyle (talk | contribs) (Created page with "* Availability and Reliability: * Orthogonal: * Systems can be unreliable but high availability * e.g. self-hosting may be more reliable because the change rate can be smaller or off-peak * Not that the failure modes are reduce, but rather that change rate is reduced * "How can you have a critical system and not control it?" e.g. GitHub * Tax Season deployments for a tax preparer software * https://incident.io/blog/we-turned-off-pub-sub-and-nobody-noticed * Scale of impa...")

21:2721:27, 6 August 2026 Resilience Coffee/2026/08/06 (hist | edit) [1,822 bytes] Kyle (talk | contribs) (Created page with "Intros: Name, Location, How you occupy your time, Topic ideas Topic ideas: Reverse Centaur Doctorow's model of how AI is changing humanity https://doctorow.medium.com/https-pluralistic-net-2025-09-11-vulgar-thatcherism-there-is-an-alternative-f1428b42a8fd Connection to Ironies of Automation: https://ckrybus.com/static/papers/Bainbridge_1983_Automatica.pdf https://www.complexcognition.co.uk/2021/06/ironies-of-automation.html Sometimes you start fighting the model to...")

16:3216:32, 17 July 2026 Resilience Coffee/2026/07/17 (hist | edit) [3,122 bytes] 65.128.100.147 (talk) (Created page with "Topics: value of code review Activities have multiple purposes Validation Accountability Control centric view Assumption: If code review goes well, then we're good Complex system view: Information sharing Repair for coordination that doesn't happen "The human mind is an eventually consistent data store" Concilable, but very tense Especially in tension when alternatives prioritize one or the other Code review as an (lesser - async) alternative to Pair Programming XP dogma...")

21:0221:02, 2 July 2026 Resilience Coffee/2026/07/02 (hist | edit) [2,264 bytes] Kyle (talk | contribs) (Created page with "* Transparency around goal framing reasons/metrics ** a paper * Success stories of safety II ** How do we _know_? ** Pushing an organization on the new view of safety * Upcoming conference: ** We Are Developers *** 40th Anniversary of Challenger Disaster * Human factors: Thomas Watson, Sr. on how we deal with people who make mistakes. * Making a case for the why of compliance ** Polishing messaging and delivery ** "For the money" ** The automated system ** D...") Tag: Visual edit

21:0521:05, 12 May 2026 Resilience Coffee/2026/05/12 (hist | edit) [2,835 bytes] 146.75.192.104 (talk) (Created page with "- Blog Post - Visualizing Systems - Some amount of mapping is value added - Without a map, domain is fuzzy - The act of constructing a map routes the thinking - "Stay where the light is" - Gary Klein: Streetlights and Shadows - "Hard pan" - tilling a field regularly leaves a field with a hard layer underneath - "Legibility" - Seeing like a State (book) - Confirmation bias - Finding the empty space with abstract maps is hard - Social construc...")

21:3421:34, 2 April 2026 Resilience Coffee/2026/04/02 (hist | edit) [2,170 bytes] Kyle (talk | contribs) (Created page with "- Preparing for interviews using coding assistants - Eating schedule as a barometer for resilience - Artemis II - Is Hardware the future? - Recycling - dogfood bags - Working with LLMs when you don't have the expertise - Nate Jones "Models amplify confidence but not experience" - You own the output - LLMs sound similar to grad students at the edge of knowledge boundaries, unable to verify hypotheses of understanding, or mirror user input speech article...")

17:0517:05, 20 February 2026 Resilience Coffee/2026/02/20 (hist | edit) [797 bytes] Kyle (talk | contribs) (Created page with "Topic ideas: - Systematizing and Dancing with Systems, when are mental models helpful vs a distraction: the map is not the territory - How polished should the fire trucks be? - Vendor side for customer fires - wishful thinking about vendors - multi party incidents - vendor relationship teams - vendor as blame sink - leaders can err in viewing vendors as complicated (lots of cogs) vs complex providers (turing machine) - expertise boundaries - Adapti...")

22:1722:17, 5 February 2026 Resilience Coffee/2026/02/05 (hist | edit) [241 bytes] Kyle (talk | contribs) (Created page with "Topics: * Higginbotham's CHALLENGER * Digital Apollo and autopilot * Normalization of Deviance * ... in Healthcare: https://pmc.ncbi.nlm.nih.gov/articles/PMC2821100/ * Inverse phenomenon https://en.wikipedia.org/wiki/Diffusion_of_innovations") Tag: Visual edit: Switched

15:4315:43, 15 December 2025 Resilience Coffee/2025/12/04 (hist | edit) [611 bytes] Kyle (talk | contribs) (Created page with "- triage when everything is on fire - accepting things you won't take action on - sign of overload - you're always triaging, it just may be implicit - everything is important until you hit a limit - Make the priorities visible - opportunity - law of stretched systems - Going Solid Resilience in ICUs <nowiki>https://ferd.ca/notes/paper-going-solid.html</nowiki> - tipping points - connection to scheduling problems - sharp edge compounds - Getting people...") Tag: Visual edit

03:1603:16, 10 November 2025 Observability (hist | edit) [69 bytes] Kyle (talk | contribs) (Created page with "The ability to infer the internal state of a system from its outputs.")
03:1603:16, 10 November 2025 Incident Command System (hist | edit) [53 bytes] Kyle (talk | contribs) (Created page with "https://en.wikipedia.org/wiki/Incident_Command_System") Tag: Visual edit
03:1403:14, 10 November 2025 Specialists (hist | edit) [56 bytes] Kyle (talk | contribs) (Created page with "Someone with specialized skills for specific situations.")
03:1403:14, 10 November 2025 Generalists (hist | edit) [61 bytes] Kyle (talk | contribs) (Created page with "Someone who has the ability to adapt to different situations.")
03:1303:13, 10 November 2025 Service Level Agreements (hist | edit) [64 bytes] Kyle (talk | contribs) (Created page with "A Service Level Objective that established between entities.")
03:1203:12, 10 November 2025 Sense-making (hist | edit) [33 bytes] Kyle (talk | contribs) (Created page with "Jointly developing understanding.") Tag: Visual edit
03:1203:12, 10 November 2025 Blamelessness (hist | edit) [113 bytes] Kyle (talk | contribs) (Created page with "An approach to Retrospectives where you explore the events that unfolded without judgement of those involved.")
03:1103:11, 10 November 2025 Adaptive capacity (hist | edit) [79 bytes] Kyle (talk | contribs) (Created page with "The ability of a system to respond to changes over time. Category:Concepts")

16:0416:04, 17 October 2025 Resilience Coffee/2025/10/17 (hist | edit) [1,534 bytes] 65.128.85.255 (talk) (Created page with "* transition from managed service to self-hosted, uptime/mttr ** SaaS -> managed -> self-hosted ** Unique per customer ** "Each deploy was an incident" ** "Professional services" -> enterprise billing model, executive sales model, additional staff per customer ** Patching, Helm charts? appliance approach? * Design/systems thinking ** User research ** Human factors ** Huge overlap with RE ** Erika Hall's "Just Enough Research" ** Sheryl Cababa's "Closing the Loop - System...") Tag: Visual edit: Switched