Here's a few random things
- 2024/04/21 — Paper: Understanding and Effectively Mitigating Code Review Anxiety
- 2024/02/10 — Paper: How audits fail according to incident investigations
- 2024/02/03 — Paper: Observation and assessment of crossing situations between pleasure craft and a small passenger ferry
- 2023/12/16 — RHIP, doctors, and pagers
- 2023/12/10 — Paper: Visualizing Uncertainty for Non-Expert End Users
- 2023/11/24 — Paper: You Want My Password or a Dead Patient?
- 2023/10/15 — Paper: How in the World Did We Ever Get into That Mode?
- 2023/10/08 — Paper: AI Art and its Impact on Artists
- 2023/09/30 — Paper: Four Concepts for Resilience Engineering
- 2023/09/24 — Paper: The Strategic Agility Gap
- 2023/09/04 — Paper: The Tyranny of Structurelessness
- 2023/08/27 — Paper: Seeing the Invisible
- 2023/08/23 — On Willpower
- 2023/08/19 — Paper: The Psychology of Incident Investigations
- 2023/08/03 — Paper: Designing for Expertise
- 2023/07/28 — Paper: Managing Without Blame?
- 2023/07/25 — Paper: Anticipatory Thinking
- 2023/07/08 — Paper: Can We Trust Best Practices?
- 2023/07/03 — Paper: Unruly Bodies of Code in Time
- 2023/07/02 — Paper: Skills, Rules, and Knowledge
- 2023/06/25 — Paper: Ecological Interfaces: A Technological Imperative in High-Tech Systems?
- 2023/06/21 — Paper: Building and revising adaptive capacity sharing for technical incident response
- 2023/06/11 — Paper: Imaginaries of Omniscience
- 2023/05/31 — Paper: Accident Report Interpretation
- 2023/05/21 — Paper: How a Cockpit Remembers Its Speed
- 2023/04/22 — Paper: Ironies of Automation
- 2023/04/18 — Accidents come from relationships, not parts
- 2023/04/11 — Paper: Distancing Through Differencing
- 2023/04/07 — Paper: Systemic Contributors Analysis and Diagram (SCAD)
- 2023/04/01 — Paper: Can We Ever Escape From Data Overload?
- 2023/03/27 — The Real World of Technology
- 2023/03/26 — Paper: Nine Steps to Move Forward From Error
- 2023/03/17 — Paper: On Nonscalability
- 2023/03/10 — Paper: On People and Computers in Joint Cognitive Systems at Work
- 2023/03/06 — The 80% League
- 2023/03/06 — On the hunt for a bug with a hump and a long tail
- 2023/03/04 — Paper: Those Found Responsible Have Been Sacked
- 2023/03/02 — Paper: Ten Challenges for Making Automation a "Team Player"
- 2023/02/26 — Paper: When mental models go wrong
- 2023/02/19 — Paper: Flexible Sketches and Inflexible Data Bases
- 2023/02/10 — Paper: Failure to adapt or adaptations that fail
- 2023/02/03 — Paper: MABA-MABA or Abracadabra?
- 2023/01/22 — Paper: Going Solid
- 2023/01/14 — Paper: Agentive Language in Accident Investigations
- 2023/01/08 — Paper: Rule- and Role-Retreat
- 2023/01/04 — Leveson on Severity
- 2022/12/17 — Paper: Sex and Death in the Rational World of Defense Intellectuals
- 2022/12/10 — How practitioners adapt to clumsy technology
- 2022/12/09 — Paper: The Alarm Problem and Directed Attention in Dynamic Fault Management
- 2022/12/08 — Paper: Visual Momentum
- 2022/12/04 — Paper: Voice Loops as Coordination Aids in Space Shuttle Mission Control
- 2022/12/03 — Paper: Managing the Hidden Costs of Coordination
- 2022/11/26 — Paper: Moving off the Map
- 2022/11/20 — Paper: Repentance as Rebuke: Betrayal and Moral Injury in Safety Engineering
- 2022/11/17 — On Theories and Tools
- 2022/11/16 — Following Procedures Dilemma
- 2022/11/12 — Paper: Past the Edge of Chaos
- 2022/11/07 — A brief history of incident models
- 2022/11/04 — Paper: Don't Let Knowledge Walk Away