Talks with Brian Troutwine
summary
Claims that everything is terrible and that the useful takeaway is how systems cope with failure not grand language theory. Recommends Joe Armstrong and Jim Gray 1986 as grounding, cites Tandem’s non‑stop examples, and gives a concrete operational claim: the two biggest outage causes are not deploying patches and deploying buggy patches. Argues Erlang’s runtime bakes supervision into apps, observes engineers often become operators and that operators are part of the system, pager duty included.
AI-written summary · about
related talks
45mKeynote: The Hitchhiker’s Guide to the Unexpected
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
41mYour Systems Aren't Stuck - Your Teams Are
48mFault Tolerance on the Cheap Making Systems That Probably Won't Fall Over
01h 00mKeynote: Over a Century of Programming
22mA Plea for Boring Tech
39mThings that Matter
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability