Thinking in Objects
summary
Argues Ruby is best approached from objects as identity, behavior, and state, not mixed procedural habits, and that the real mechanism is messages with late/dynamic binding. Recommends encapsulation and polymorphism (duck typing) over passing hashes-with- type and giant case statements. Advises composition/delegation instead of deep inheritance, shows a concrete refactor: collapse a three-level conditional by adding aliases to a Variant class so the same scope message dispatches polymorphically. Warns against calling methods directly via bound Method objects.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:59OOP core concepts
- 8:07Object identity behavior state
- 13:25State encapsulation uniform access
- 16:33Polymorphism duck typing
- 17:17Object-based vs OO languages
- 18:22Inheritance risks alternatives
- 21:08Delegation vs inheritance Ruby
- 23:16Message passing importance
- 25:46Ruby programs use objects
- 27:31Reification behavior attractors
- 29:40Polymorphism in Ruby
- 33:14Summary call to action
