The Value of Objects -
summary
Shows concrete bugs avoided by turning primitives into small immutable types: constructor-parameter swaps, fragile email parsing, and wrong money math for odd currencies like Mauritania’s 1/5 unit. Claims IDs are always value objects and demonstrates money as major/minor units with currency metadata and a currency pool for common types. Recommends cross-platform generation with Google Protobuf and Java helpers like AutoValue/Lombok/Kotlin to produce usable VOs that prevent these errors.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 0:44Problems with primitive modeling
- 3:19Currency representation challenges
- 5:09Value objects explained
- 7:23IDs as value objects
- 9:15Tools for value object adoption
- 10:39Summary and key takeaways
related talks
29mSingle Value Objects: where DDD and Functional Programming Share Forces
32mUndervalued: The Most Useful Design Pattern
45mBeyond design patterns and principles - writing good OO code
59mThe Most Valuable Values
47mSpring, Hibernate, the Value Object Pattern and the Limits of Its Use
32mThe Evolution of Object-Oriented Programming
01h 02mObjects vs Values: Value Oriented Programming in an Object Oriented World
01h 42mValue Oriented Programming Part V - Return of the Values