Design Patterns: Elements of Reusable Object-Oriented Software
December 27th, 2006
For quite some time I have used classes and objects but only did so for namespace control. They were more or less an annoyance. Everyone says OOP is a good pattern (or paradigm) for modeling problems. We've all seen the diagram of doughnuts floating in a pond where the outer ring represents methods and the inner circle represents data or state. The question of how to best set up my pond and where to put the biggest doughnuts never had a solid answer. I suppose folks with experience using frameworks have seen design patterns in action and already know how to build a good foundation. I had no idea until I got a hold of this book, which incidentally had been on the shelf in the office for like two years. It belonged to my wife but now belongs to me. I actually decided to marry her to own this book for myself. I now see other peoples code in a whole new light.
Your Response