Function reuse is just wishful thinking
summary
Claims that practical code forces Functor/Apply/Applicative/Monad patterns and offers a design trick called wishful thinking that makes “someone else” build the missing bridge. Starts from a PS5 crawler and implements concrete functions: affordable, cheapest, totalCost, flip (List[F[A]] → F[List[A]]), flatten/flatMap; shows lift / map, apply / applicative, flatMap / monad as the actual tools. Demonstrates these compose to reuse one core function across Option/Future/Try and that the approach actually works.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 2:55Functors explained
- 10:46Applicatives and apply
- 19:33Applicatives in depth
- 27:29Monads and flat map
- 37:33Summary and conclusion
related talks
53mFunction Reuse is just Wishful Thinking
01h 06mThe Functional Programmer's Toolkit
01h 16mFunctional Composition Beyond Monads
35mThe Functor, Applicative, Monad talk
58mMonoids, Monads, and Applicative Functors: Repeated Software Patterns
01h 14mBeyond Free Monads
43mFunctional Programming with Effects
58mFunctional Programming with C#