A Decision Maker's Guide to Typed Functional Languages
summary
Companies report concrete wins: Jane Street runs 30 million lines of OCaml with ~500 engineers and uses types to reduce catastrophic trading errors while Standard Chartered maintains ~6.5 million lines of Haskell across ~40 engineers for safer risk models; product startups using Elm (Corvus, Vendr, NoRedInk, Brilliant) cut frontend runtime exceptions from tens of thousands to near zero, enable non‑engineer content authors, and reach full productivity after 4-week onboarding, letting teams ship more features with far fewer bug fixes.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:30Engineering department
- 2:57Case studies
- 3:41Case study: Jane Street Capital
- 12:28Case study: Standard Chartered
- 18:34Case study: Corvus Insurance
- 22:25Case study: Vendr
- 27:15Case study: NoRedInk
- 33:29Case study: Brilliant
- 35:32Conclusion: Developer efficiency
- 36:20Conclusion: Retention
- 36:45Things to know
- 38:11Things to ask
- 40:39Outro
related talks
54mQ & A Session With Functional Conf Speakers
47mHow to Grow More Functional Programmers
01h 18mA Tale of Two Lambdas: A Haskeller's Journey into OCaml
57mMaximising Side Effects When Adopting Functional Programming
26mAn Invitation to OCaml
01h 47mFunctional C++
43mOCaml at LexiFi
58mKeynote: Why Functional Programming Matters