Systematically handling errors in your code to make them useful
summary
Shows using typed errors and dedicated error channels so the compiler forces handling, demonstrating ZIO in Scala and its adoption in Rudder to replace exception-driven code and reduce boilerplate. Presents a staged license-validation pipeline (read file → parse → verify signature) where each step narrows types and funnels failures into a single typed error channel, yielding structured operational context, full developer traces, actionable user messages, safer composition and resource handling, and production readiness.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:45Error handling cost
- 5:37Error inventory
- 10:32Clear contracts and models
- 17:16Systematic code handling
- 26:26Compilers and automation
- 31:01Actionable error signals
- 34:55Least resistance path
- 38:48High-level tools
- 46:21Q&A
related talks
44mInitiatory Journey from Exceptions to Composable Error Types
17mA closer look into error handling techniques
48mTDD, Like in Type Driven Development
49mBuilding Safe, More Testable Scala Production Systems
31mProgramming Safely in an Uncertain World
49mError handling architecture: clean, rapid, reactive approach
22mScale By The Bay 2018 Unconference: Omer Van Kloeten
25mEn route to better code