A Skeptic's Look at Scalaz Gateway Drugs
summary
An engineer replaces ad hoc error handling on an API server with Scalaz primitives and shows what actually changes: converting Option to \/ (disjunction) to preserve failure messages, using Validation to accumulate multiple errors instead of short‑circuiting, and grouping errors in NonEmptyList so clients get a list not a globbed string. The setup runs on a production‑style service, fixes opaque 500s from bad JSON, and yields clearer, aggregating diagnostics that reduce debugging time.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:20Scholars Ed 101
- 1:25Skit
- 1:44Validation and Scholars Ed
- 2:09Skepticism
- 3:40Magic
- 4:20The Road
- 5:49Scholars Ed
- 6:29Problems to solve
- 8:07Help developers help themselves
- 10:50Dont worry
- 11:00Scholars EDD
- 12:05Right Bias
- 12:36Type Notation
- 14:01Option
- 14:34Options in Scala
- 15:53Disjunction
- 16:27Disjunctions
- 17:28Expression
- 18:16Validation
- 19:14New Users
- 19:41DBUser
- 20:05ValidDBUser
- 20:22Address
- 20:46Post Office Validation
- 21:04Combining Validation Results
- 23:28NonEmpty List
- 24:40Pipe at Pipe
- 25:24Naming
- 26:04Oink
- 26:41Learning Scholars Ed
- 27:47Pinkie Pie
related talks
37mA Skeptic’s Look at scalaz’ Gateway Drugs: A Practical Exploration
29mLearning Scalaz
28mAutomating API Busywork with Scala
09m1000+ Compile-time Errors Later and Running Smoothly in Prod
59mMinimizing the Slippery Surface of Failure
31mSCALATEST: YOU'RE ASSERTING IT WRONG
31mCool toolz in the Scalaz and Cats toolboxes
28mMaking the Impossible Impossible: Improving Reliability by...