Velocity 2012: Richard Cook, "How Complex Systems Fail"
Channel:O'Reilly · Length:28:20 · Published:2012-06-27 · Views:60365
Summary
Dr. Richard Cook, a physician and patient safety researcher, presents his ideas on how complex systems fail, at Velocity 2012. He argues for designing for resiliency rather than trying to exhaustively handle every failure mode.
Why HN recommends it
HN people recommend it as a must-watch for anyone running complex systems, and some rewatch it regularly to remember its principles.
I would watch this talk every couple of months to remind myself of the principles. — HN, 2020
Distributed systems · Cloud, DevOps & reliability
Subtitles (excerpt)
thank you very much um it's great to be here and thank you very much for the kind invitation um this is not my usual audience um and so you'll forgive me if we get things wrong a little bit if we uh confuse things or get them um uh a little off key um it's because I'm not one of you guys uh on the other hand uh a lot of what we experience I think is pretty much in common um and there is a kind of resonance between the sort of research that I do and that my colleagues do and the kinds of experiences that you have um particularly with systems uh and their complexity and failure the title of this talk is build is is how complex systems fail but I'm not going to talk about that because there isn't enough time uh so I'm going to talk about how complex systems don't fail and and the reason is because it's something that we don't look at very often we we're pretty attuned to failure but we don't look at at success very very frequently at least in an operational setting those of you who work in operations know that nobody ever calls you calls you up on the phone at 3:00 in the morning to see that the system is running well and they're very happy with things so the the outline of this talk is pretty simple I'm going to tell
On Hacker News
The accompanying talk by Richard I Cook at the O'Reilly Velocity conference is here: [VIDEO] When I worked in operations, I would watch this talk every couple of months to remind myself of the principles. The principles are summarized in the list, but the talk adds a bit more context. I find that this context matters for seeing how the principles might be applied. — wenc, 2020-12
> We should probably be doing modelling and formal verification and stuff like that. This is interesting. Is this a hypothetical notion or can you share any personal experience of having worked on any projects where this is done successfully? I bring this up because there is typically a narrow band of applicability of purely theoretical constructs in most complex systems (AWS & Azure teams both u… — wenc, 2019-01
To build on this discussion, what are some highlights in that book that you found useful? I ask because I've read some systems thinking books (e.g. Systemantics) that were difficult to apply in real life. I come from the perspective of someone with a systems/theory builder personality. The only systems thinking book that I found remotely practical was The Fifth Discipline by Peter Senge. The most… — wenc, 2019-01
Richards Cooks How complex systems fail from velocity a couple of years ago [VIDEO] and the paper that's the basis for it is also nice to have handy [LINK] — hedwall, 2017-02
except every single good thing we have is built upon failure. got a gsm phone? broadband? how about a modem? a pc? basic chemistry? cryptography? the very notion of cryptography is embracing the failure of having private data leaked. did you know 802.11 was initially made for infrared? do you remember how much it sucked? maybe if would have progressed faster if it was out in the wild faster. that… — rjzzleep, 2013-01
Related videos
- Why is Ukraine the West's Fault? Featuring John Mearsheimer · The University of Chicago · 1:14:15
- What Languages Sound Like To Foreigners · Sara Forsberg · 1:44
- COVID-19 Vaccines: MODERNA | PFIZER/BIONTECH | ASTRAZENECA · Ninja Nerd · 43:40
- Michael Stonebraker | Big Data is (at least) Four Different Problems · Michigan Engineering · 55:53
- The Man Who Took LSD and Changed The World · Veritasium · 33:39
- The Soul of Erlang and Elixir • Sasa Juric • GOTO 2019 · GOTO Conferences · 42:02
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 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
- AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401) · Amazon Web Services · 59:56
- Erlang Factory 2014 - That's 'Billion' with a 'B': Scaling to the Next Level at WhatsApp · Erlang Solutions · 49:15
- "Turning the database inside out with Apache Samza" by Martin Kleppmann · Strange Loop Conference · 47:42
- The Language of the System - Rich Hickey · ClojureTV · 1:02:49
- Google I/O 2012 - Go Concurrency Patterns · Google for Developers · 51:27
- Literate Devops with Emacs · Howard Abrams · 28:36
- Conflict Resolution for Eventual Consistency • Martin Kleppmann • GOTO 2016 · GOTO Conferences · 51:35