Who Destroyed Three Mile Island? - Nickolas Means | The Lead Developer Austin 2018
Channel:LeadDev · Length:37:06 · Published:2018-03-21 · Views:762565
Summary
Nickolas Means recounts the 1979 Three Mile Island accident minute by minute, from the control rod insertion to the operator's decision to switch off emergency cooling. He argues that finding systemic causes is more useful than blaming individuals.
Why HN recommends it
HN recommends it whenever a failure is blamed on human error, as a clear case study in looking for the systemic second story.
There's an excellent talk from Nick Means (GitHub) called "Who Destroyed Three Mile Island?". — HN, 2021
Software practice, open source & careers · Cloud, DevOps & reliability · Nuclear power & fusion
Subtitles (excerpt)
[Music] [Music] so I will start by pointing out that the giant 18 t cell mask that's over there is because of South by and so like most things in Austin right now the problem with the microphone today is South by his fault so thanks for that interim area that was very kind you're always way too kind I really appreciate it I really love what Mary and Ruth and the whole team at White October have built in this event I think it's something that those of us that care deeply about leading well really needed and so I'm thankful it exists in the world so thank you for all the time and effort and attention that you put into it I'm especially excited and thankful yeah please I'm especially excited and thankful that they brought it to my home town of Austin and I am incredibly honored to be on this stage tonight so when I was a kid my parents gave me this for volume set of books called how things work my dad is a mechanical engineer by training and I think the reason they gave me this set of books is because he got tired of answering all of my complicated questions about how things work maybe it was that maybe it was that he wanted to teach me to get these answers on my own I don't have a chance to look at these books very often these days
On Hacker News
There's an excellent talk from Nick Means (GitHub) called "Who Destroyed Three Mile Island?". Link: [VIDEO] One thing it discusses is how the alerts inside the control hub were so noisy, and were logged via a reasonably slow printer, that the alerts which suggested the reactor was in serious trouble only printed hours after you could do anything. And the alert light that said "shits fucked" was p… — lawrjone, 2021-02
Nickolas Means has an absolutely wonderful set of talks on themes like this. Particularly relevant here I think, is his talk: "Who Destroyed Three Mile Island?" - which goes through the events that occurred at the nuclear power plant, the systemic problems, and how to find the "second stories" of why failures occurred. [VIDEO] — Huggernaut, 2020-10
Thanks for that, I really appreciated this breakdown of the accident at Three Mile Island and the concept of 'the second story' with regards systems thinking; [VIDEO] — tudorw, 2024-01
I'll have to dig up a citation. But the [] Three Mile Island accident was in part caused by (former) naval nuclear specialists making poor choices based on optimizing for the wrong things. My memory is fuzzy, but this 37 minute video [2] has a breakdown. If memory serves, the root causes were faults in the pumps and delays in the 28 baud diagnostic printouts running minutes or hours behind which … — codebeaker, 2021-05
Related videos
- Zarch (1987) Gameplay for BBC Acorn Archimedes High Quality · Phoenix Risen · 8:59
- The Extreme World of Ultra Intense Lasers - with Kate Lancaster · The Royal Institution · 59:18
- Domain Modeling Made Functional - Scott Wlaschin - KanDDDinsky 2019 · KanDDDinsky · 50:49
- MIT's Pathway to Fusion Energy (IAP 2017) - Zach Hartwig · MIT Plasma Science and Fusion Center · 1:11:39
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor The Future of Programming · Joey Reid · 32:55
- Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems" · O'Reilly · 19:09
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Uncle" Bob Martin - "The Future of Programming" · Paul Stringer's Mobile Tech · 1:18:21
- AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · Amazon Web Services · 59:56
- Breakthrough in Nuclear Fusion? - Prof. Dennis Whyte · MIT Club of Northern California · 1:38:48
- Tim Ewald - Clojure: Programming with Hand Tools · ClojureTV · 58:39
- Using Python to Code by Voice · Next Day Video · 28:17
- Transforming Code into Beautiful, Idiomatic Python · Next Day Video · 48:51
- Agile is Dead • Pragmatic Dave Thomas • GOTO 2015 · GOTO Conferences · 40:39
- Literate Devops with Emacs · Howard Abrams · 28:36