<< 1 >>
Rating: 
Summary: Pattern articles capture expertise!
Review: I was at the PLoP conference where the articles in this book were written (mine is number 24). It's a writers' workshop where each paper is metaphorically ripped in shreds and then reassembled, better than before. We worked hard to make these patterns right. Did our work pay off? You better believe it. I've read this book and the first in the series both cover to cover, and the best of this book is equal to the best of the first one. The average quality is higher. Buy it just for Crossing Chasms, a comprehensive look at all the headaches you get when you try to marry relational databases to object systems. Or buy it just for Demo Prep, which will tell you how to achieve your goals with software demos - happy customers, happy programmers. Or maybe you need to read my article, Patterns for Classroom Education, which tells you how (and why) to design a course to teach computer programming - or any technical skill.
Rating:
Summary: Pattern articles capture expertise!
Review: I was at the PLoP conference where the articles in this book were written (mine is number 24). It's a writers' workshop where each paper is metaphorically ripped in shreds and then reassembled, better than before. We worked hard to make these patterns right. Did our work pay off? You better believe it. I've read this book and the first in the series both cover to cover, and the best of this book is equal to the best of the first one. The average quality is higher. Buy it just for Crossing Chasms, a comprehensive look at all the headaches you get when you try to marry relational databases to object systems. Or buy it just for Demo Prep, which will tell you how to achieve your goals with software demos - happy customers, happy programmers. Or maybe you need to read my article, Patterns for Classroom Education, which tells you how (and why) to design a course to teach computer programming - or any technical skill.
Rating: 
Summary: Rich for ideas, poor for effective solutions
Review: The article gathered here are essentially alexandrian like papers, where general ideas and goals appears clearly, but expressed in a very textual way. So, there is not a lot of stuff on effective design patterns. Hopefully there is some (and even good ones), but it's not obvious that it justify the book size. If you are rather new to patterns (you've just read the "Design pattern" and / or "Pattern oriented software architecture"), consider first the third volume. If you like it, then consider to buy this one. If you REALLY REALLY like it, then consider to buy the first volume
<< 1 >>
| 
