OSFeels 2016 - Complex System Failures and Blameless Retrospectives by Courtney Eckhardt
489 views · Published 18 August 2016 · 21:43 · Indexed 30 October 2026
Channel: Confreaks · 2016 · Science & Technology
OSFeels 2016 - Complex System Failures and Blameless Retrospectives by Courtney Eckhardt Seattle has two of the longest floating bridges in the world, and in 1990, one of them sank while it was being repurposed. To this day, the public reporting on the failure is extremely simplistic and full of fingerpointing- but the official investigation found that there were five factors involved and all of them were required for the bridge to fail. This accident was a classic complex systems failure, and there are a lot of really interesting things to learn both from the official findings and from the difference between those findings and the public coverage. In the era of The Cloud and services like Wikipedia, more and more of us are going to be dealing with complex system failures and trying to understand what happened. When we ask "what happened?", the language most people answer with carries implied blame- we find ourselves talking about who made a mistake and what they should have done instead. But this doesn't help us understand what changes we can make to actually change the chance of experiencing that failure again and we don't learn how to make our systems more robust by suggesting that people not make mistakes. It's possible to do better and to be better to ourselves while we do it. Help us caption & translate this video! http://amara.org/v/UkZR/
More from this channel
-
35:52
Code Design and the Science of Pleasure
-
48:58
Ruby Software Continuously Delivered and Exhaustively Explained by Brian Guthrie, Srushti Ambekallu
-
40:58
Jruby Polyglot Heaven by Thomas E Enebo and Charles Oliver Nutter
-
42:17
Be a Minecraft modman with Purugin by Thomas E. Enebo
-
36:46
Your tests are lying to you by Chris Parsons
-
23:46
KidsRuby: Think Of The Children! by Ron Evans
-
52:05
Resources, For Real This Time (with Webmachine) by Sean Cribbs
-
38:28
Just Say No To :nodoc: and Document Your Code! by Loren Segal