Teaching functional programming in the ivory tower ... and in the kitchen
summary
Panel compares concrete training tactics and outcomes: industry teams adopt Scala in 2014 to tackle concurrency, distribution and eventual consistency, with onboarding plus 3–6 months to reach productivity; universities run intensive week modules or a 42‑module part‑time masters to teach applied FP; suppliers run ~40 paid corporate courses over two years and ship templates via SBT and GitHub to beat blank‑page syndrome; successful exercises are web servers, React/Redux front‑ends and domain‑specific languages that expose composability and immutability.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:35Eugenia Cheng
- 9:28Most difficult case
- 13:13How I got into category theory
- 20:56The problem with mathematicians
- 22:16Programming in math
- 23:57Learning functional programming
- 28:38Teaching functional programming in the ivory tower
- 32:25Motivation
- 33:44Programming in Haskell
- 37:09Teaching people who dont wanna be there
- 40:17About Radium Barcelona
- 48:45Teaching at Oxford
- 50:35Teaching software engineering
- 56:42QA
related talks
57mThe Fun of Functional Programming Panel
01h 00mWhat The Functional Programming
43mFunctional Programming in Practice with Kotlin & Scala
38mFunctional Programming - The Architecture of Choice
01h 44mFunctional Programming: Technical Reasons to Adapt
49mRelax, It's Just FP
59mFunctional Programming for Machine Learning Panel
36mConcrete Functional Programming