An Object-Oriented Example

If you’ve been reading this newsletter for a while, you’ve may have noticed there are two patterns I talk about all the time:We’re doing something because everybody does it but we don’t know why.We’re doing something, but we don’t really believe in it so we’re doing it halfway and not getting any benefit.Object-Oriented Design often hits both those patterns – teams use OO languages for various reasons without thinking about what OO can do for them, and then teams don’t use OO design or programming tools in a way that can help them achieve their goals.