From OOP To FP
summary
Explains a practical path from OOP to FP in Kotlin, showing the team’s year‑long migration and concrete wins: purer functions that simplify unit tests, immutability yielding easier concurrency, and memoization/parallel map opportunities. Recommends small habits — start with use val, run a 30‑day challenge to avoid loops and if — and uses Arrow‑KT types (Either, Option, IO) to model errors and effects. Side effects live at the outer boundary (roughly 90% functional, 10% imperative), and the converted samples run and test cleanly.
AI-written summary · about
chapters (19)
- 0:00Introduction and motivation
- 3:46Unlearning OOP bias
- 8:17Declarative vs imperative
- 11:06Explicit return types
- 14:40Immutability benefits
- 17:11Pure functions explained
- 20:47Referential transparency
- 24:44Isolating side effects
- 26:30Function composition
- 27:14Exception handling in FP
- 28:57Avoiding classes for logic
- 31:53FP and OOP coexistence
- 33:20Daily functional habits
- 36:50Eliminating if conditions
- 38:18Caveats and gradual adoption
- 40:43Libraries like Arrow
- 41:25Handling exceptions with Either
- 42:48Option types and nulls
- 43:31IO for side effects
