Communicating in Types
summary
Argues that modern type systems act as a readable design language and demonstrates concrete wins: uses Elm code from a heat‑map startup (payment flows, Google Maps integration) to show algebraic data types and enums modeling success/failure cases, fixes a buggy icon helper by changing string→string to a typed Icon→Html signature, shows the compiler catching a missing view case, and refactors a monolithic createInvoice into fetchInvoice + generatePDF to reveal read vs write DB needs (algebraic data types, read-only context). Recommends Haskell, PureScript, Unison for exploring further.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:42Disclaimer
- 2:05A story of types
- 3:59Describing things
- 11:22Describing relationships
- 15:08Some examples in Elm
- 23:49Describing context
- 32:46Where next?
- 35:44Outro
related talks
47mCommunicating in Types
39mCommunicating in Types
34mCommunication, Expression, and Types: Your Compiler as an Ally
38mType Systems - The Good, Bad and Ugly
49mThe Trouble With Types
30mBetter Code Design with Types and Concepts.
30mSwipe Left, Uncaught TypeError Learning to Love Type Systems
33mPurifying Typescript