Trust, but Verify
summary
Argues that Elm already delivers practical correctness: a NoRedInk codebase runs 100k lines, zero runtime exceptions in production; the Elm compiler drives refactors by surfacing 16 simple error messages when changing a core type so the app recompiles and works immediately; built‑in property‑based testing and fuzzing catch real bugs (one example finds JSON timestamp truncation); elm-package enforces semantic‑version bumps automatically; elm-format gives a single, machine‑blessed style.
AI-written summary · about
chapters (15)
- 0:00Introduction and setup
- 1:04Future of programming and correctness
- 2:08Chess and human-computer collaboration
- 4:16Programs helping write programs
- 5:18Elm language overview
- 6:22Elm type system benefits
- 11:26Handling nil with Maybe type
- 16:45Elm vs Ruby codebases
- 17:47Personal Elm app refactor
- 21:59Compiler-assisted refactoring
- 22:21Property-based testing
- 27:13Fuzz testing in Elm
- 28:14Semantic versioning in Elm
- 30:01Elm Format and consistency
- 31:43Brains for ideas not memory
related talks
33mTrust, But Verify (Programmatically)
39mSteal This Talk: The Best Features Ruby Doesn't Have (Yet)
44mA Completely Unbiased Showcase of Elixir
23mElixir: Happy Developers and Scaleable Backends
01h 00mTesting Heresies
40mTechniques for Metaprogramming in Erlang
39mElixir: Power of Erlang, Joy of Ruby
33mBefriending the Turtles