Morning Keynote: Embracing an Error-Prone Reality
summary
Second Spectrum builds optical tracking and analytics for the NBA and LA Clippers and runs full‑stack data visualizations that must stay up under load; Elixir and Erlang are credited with 99.999999% uptime on a flagship Ericsson system (about half a second downtime over 20 years). The concrete claims: message‑passing concurrency and immutability reduce failure modes; Elixir gives Elixir pipes and mix and formatter tooling that make Erlang’s failure‑accepting model practical; Elm’s type messages reduce runtime errors.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:35About Second Spectrum
- 1:46Why we love Elixir
- 3:55Agenda
- 7:37Errors are unavoidable
- 9:50Erlang
- 10:40Shared State Concurrency
- 12:58Message Passing Concurrency
- 14:37Concurrency
- 16:55Hangul
- 20:50Easy mnemonics
- 24:07Erlang and Elixir
- 25:18Pipes
- 26:06Example
- 27:29Other benefits of Elixir
- 29:29About Elixir
- 30:50About Error Messaging
- 33:58Conclusion
- 34:24A paradigm shift
- 34:51Polish example
- 36:34What have we learned
- 38:05John Perry Barlow
related talks
29mEmbracing Failures to Avoid Meltdown
35mKeynote: The Unfortunate Value of Failure
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
53mClosing Keynote
05mAaron Aldrich - DevOpsDays NYC 2018 Ignite
17mIf You’re Happy and You Know It (Inside the Mind of a Developer)
54mRuin Your Systems By Making Them Perfect
47mThe art of challenging assumptions