I hate computers. How many times have you heard those words? Or said them yourself. Systems crash and go boom all the time. The easiest thing to do is to blame the person touching the keyboard when it happens. Especially when that person touching the keyboard is you. But how do we build safer systems? How do we build humane systems, systems that actually engage and even delight the user? Sidney Dekker says "Safety improvements come from organizations monitoring the gap between procedures and practice". How can you build a system for safety if the way the system is designed isn't actually how it's used. Of course it doesn't work, you were doing it wrong. We have to stop shoving users into systems with procedures that aren't based on reality.
In this talk I address these questions through my experience building tools for developers. Every tool works in an ideal world and on my machine. But the hard part is building tools that "work" even when they don't. Understanding the gap between procedure and practice can be a real challenge, and if you don't approach that problem with a big dose of empathy you won't have much luck closing that gap.
Important Note: In this talk I conflate the idea that Safety I & Safety II and the Old View/New View are equivalent ideas. That is incorrect, what I was mostly talking about in that section of the talk is Dekker's New/Old Views on Safety. If you're interested in learning more about Erik Hollnagel's Safety I and Safety II check out his paper http://www.resilienthealthcare.net/A_tale_of_two_safeties.pdf
Thanks to John Allspaw for so kindly pointing this out to me.
Video Link: https://www.youtube.com/watch?v=ZFdN20G65NA&feature=youtu.be