Learning From Our Elders: Applying functional insights without losing Swift
summary
Claim: Swift is not purely functional but borrows concrete functional lessons. Shows how to build small composable datasources instead of fat view controllers, how to prefer strong domain types (IDs, tokens) over loose strings/dictionaries, and how enums with associated values produce a Result<Token, Error> style API that compiles wrong before it runs. Demonstrates using protocols, structs, optionals, generics, type lifting, and never/void to make illegal states impossible so fewer corner-case tests are needed and behavior is easier to reason about.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:57Swift is not functional
- 5:19Using composition
- 9:09Models and views
- 12:14Putting the pieces together
- 19:02Strengthening types
- 21:42Weakest types
- 27:49Most abused types
- 33:09Protocols
- 38:24Types
