So I hurried through this book as to immerse oneself in it would take months. Plus, the majority of the patterns mentioned are just formalizations of ideas that I have come across naturally throughout my programming career. At the same time, I wanted to read it to fully familiarize myself with the terminoligy and maybe pick up on some new concepts. Honestly, I have to think that there are better design pattern books out there that explain them in a more concise and obvious manner than this book does. The book is now dated by 13 years which is several generations in software life. This is the grand-daddy of design pattern books and must be given its due respect. I don't own the book, and I am still undecided on whether or not I will purchase it to keep as a reference. As I said, there have to be better design pattern books out there. However, for the time being, I am done reading about design patterns and am moving on to Debugging .NET 2.0 Applications for February.