~/talk

How OOP Earned Our Trust and Let Us Down

Talkat Scala Days 2026 · 2026-10-12..10-13· [scala, software-architecture]
links:none on file
slides:none on file

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

  1. 0:00Introduction and context
  2. 2:17The role of the engineer
  3. 5:41Pitfalls of design patterns
  4. 6:57The evolution of OOP
  5. 10:45Overengineering examples
  6. 12:31Practical case study
  7. 15:28Balancing abstractions
  8. 17:13Functional programming lessons
  9. 20:26Limits of FP and dependencies
  10. 24:16AI and vibe coding
  11. 26:06Final advice and conclusion
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.