Bringing Functional Programming to Work
summary
Advocates run workshops, reading groups and structured lessons and insist exercises are mandatory; curriculum size, frequency, TAs and homework policy determine uptake. Projects include a real-time dashboard built in Clojure that ships and helps sell the idea, and a later attempt to rewrite the main app and roll back when management forces a return to Rails. Team buy‑in, incremental low‑risk pilots, Elixir/Phoenix or Scala tooling, and translating benefits into ROI and fewer production bugs decide whether adoption succeeds.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:14Who are we
- 3:13Content
- 5:12Learning
- 6:25Avoid this
- 7:45Learning options
- 8:35Classroom environment
- 15:35Study groups
- 20:13Challenges
- 24:02When to compromise
- 28:51Dont be that guy
- 29:47The Joy of Closure
- 33:40First Production Projects
- 34:52Risk Management
- 36:51Resources
related talks
57mMaximising Side Effects When Adopting Functional Programming
34mFunctional Programming: The Enterprise Edition
53mBring FP to Work
48mFunctional Programming: The Enterprise Edition
01h 26mEconomic Argument for Functional Programming
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
09mStop the Software Apocalypse with Functional Programming
01h 01mArchitecture Decisions: A Case Study -
