How OOP Earned Our Trust and Let Us Down
summary
Claims that OOP earned reuse but breeds shared mutable state, fragile hierarchies, and accidental complexity, supported by Scala adoption stories where teams port Java habits into Scala and recreate the same mistakes. Concrete examples: a GitHub-grade FizzBuzz Enterprise Edition and a Spark-backed FizzBuzz that add clusters for trivial work, a legacy storage migration that balloons into heavy enterprise-integration plumbing then gets thrown away, and a mutable→immutable performance flip where changing collection mutability measurably improves throughput. Advice: prefer explicit effects, composition over inheritance, smaller libraries, and measure maintenance cost.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 2:17The role of the engineer
- 5:41Pitfalls of design patterns
- 6:57The evolution of OOP
- 10:45Overengineering examples
- 12:31Practical case study
- 15:28Balancing abstractions
- 17:13Functional programming lessons
- 20:26Limits of FP and dependencies
- 24:16AI and vibe coding
- 26:06Final advice and conclusion
