Error-free Elixir
summary
Claims concrete tactics for removing routine errors in Elixir by changing operation semantics rather than adding handlers: use defaults instead of returning not found errors to avoid missing settings, make commands idempotent so canceling a job returns success on repeated calls, and treat real world mismatches as observable events to collect metrics instead of blocking the user. Uses Elixir primitives like error tuples and supervisors, databases and retries, and reports these patterns shrink error-handling code, simplify tests and work in production systems.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:06ERROR-FREE ELIXIR
- 0:41Error handling is a big source of complexity
- 4:59error tuples
- 7:34Eliminating errors
- 14:22Design is not about a single clever idea
- 15:05A set of clear and simple heuristics and questions is really helpful
- 16:03Share the process of making decisions
related talks
37mElixir - functional, concurrent, distributed programming
41mIdioms for building fault-tolerant applications with Elixir
47mElixir for curing product development pains
42mIt's about (run)time -- Elixir beyond the hype
47mElixir for curing product development pains?
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
22mRefactoring Elixir for maintainability
03h 19mWorkshop - All Aboard The Elixir Express!