The Tension Between Expediency and Correctness
summary
Argues that Elixir on the Erlang VM lets teams get both speed and correctness: stateless response times drop 100 ms to 4 ms, an actor/concurrency model plus immutability avoids shared-state bugs, and a WebSocket real‑time driver-tracking service ran eight months with zero failures after deployment. Recommends concrete tools: dialyzer and quickcheck, tracing and hipe compilation, and Elm or Flow for frontend typing to catch bugs before production.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:30BUILDING SOFTWARE BETTER (and maybe building better software)
- 1:04THIS IS WHAT YOU SPEND YOUR LIFE DOING
- 3:3610 MILLION MINUTES/DAY
- 4:12YOUR SOFTWARE KILLS A HUMAN EVERY FOUR DAYS
- 4:32OBLIGATION
- 6:19CONCURRENCY
- 8:26ACTOR MODEL
- 10:20TRANSITION?
- 10:59ELIXIR
- 13:03IMMUTABLE
- 14:59CONCURRENT
- 16:55FAULT-TOLERANT
- 18:57DIALYZER
- 20:07QUICKCHECK
- 22:28TRACING ERLYBERLY
- 23:39JUST NEAT STUFF
- 25:34UNDEFINED
- 31:46QUESTIONS ON THIS PART?
- 33:10BNF BACKUS NORMAL FORM
- 34:05CAN PROGRAMMING BE LIBERATED FROM THE VON NEUMANN STYLE?
- 34:59ALAN TURING
- 35:23JOHN VON NEUMANN
- 38:54(reduce +) (map *) zip
- 41:37NO ASSIGNMENT
- 42:20COMPOSITION
- 42:51ALGEBRA
- 43:43TAKEAWAYS
- 43:55STOP THE MURDER
- 44:28TRY ELM
- 45:46THINK FUNCTIONALLY
related talks
37mModern Abstractions and the Web, and avoiding Pitfalls because Life is short
47mElixir for curing product development pains
47mElixir for curing product development pains?
37mElixir - functional, concurrent, distributed programming
49mKeynote: How to sell Elixir (Again)
41mWriting Reliable Web Apps With Elm
43mThe Tyranny of Structurelessness
42mConcurrency Oriented Software