![]() |
| |||||||||||||||
|
Rent Your Textbooks
Save up to 70% when you rent your textbooks on Amazon. Keep your textbook rentals for a semester and rental return shipping is free. |
Product Details
Would you like to update product info or give feedback on images? |
Let me put it simple: If you want to learn to think in objects, don't just read the book, do it!
If you have read "Refactoring: Improving the Design of Existing Code" by Martin Fowler et al. then you'll recognize the thougts presented in this book. In this book the patterns are close to refactorings with a bunch of simple, good, readable and understandable advices to just about every little thing - it's more than a simple style guide: You'll always get told what the raison d'etre is - and if not, where to look for it.
I'm currently using the book as a reference for style of OOP. From a teaching point of view, the book is also extremely useful. Kent Beck likes to ask quistions in a heuristic manner. Because of the simple approach to every day experiences of developing, all the way down to the experiences of beginners, you won't have any trouble answering these quistions. In fact you'll probably start asking quistions to yourself likewise because of the magnicifent way this mind trick works for your way of thinking in objects (or otherwise).
As a developer - doing these patterns - you'll be amazed at how much little things can mean in a much bigger and more complex context, when you develop systems applying OO - especially huge systems.
I am compelled to repeat: Don't just buy it, do it!
Kent's book is a pleasant, readable mix of the obvious that beginners need to know and the clever that experienced Smalltalkers can still learn from. I was surprised at the absence of Booby Woolf's strategy for classifying instance variables (as identity, status or cache; see The Smalltalk Report, June 96) and at how little there was on protocol naming. Otherwise, it seems to cover almost everything at its chosen level (which complements, instead of competing with, that of books like the Smalltalk Design Patterns Companion).
I currently use C++ on UNIX in practice (wish there were more Smalltalk & Objective-C jobs out there), but I would still highly recommend this book for any OO-Practitioner: the lessons here can be applied to many different scenarios.
Take this chance to observe the beauty of PURE OO - concise code with the semantic richness and clarity reminiscent of poetry... ...alas, if only code at work were so well crafted!
This is a handbook of OO Programming. Patterns are broken into the following categories: Behavior, State, Collections, Classes, and Formatting. Each pattern is given a question/problem that the pattern answers/solves and references to other patterns are shown with page numbers.
It's definitely one of those rare books that I return to over and over again... ...a classic.
I am using this book heavily for all software projects I'm in. Instead of wasting time on deciding how to code things, just look at the patterns, then decide and code. The patterns presented in the book simplify software code maintaintenance.
With a little work, many patterns in this book can apply to Java as well.
Kent Beck is probably one of the best thinking developers in the industry, appropriately combining theory and practice to produce results with elegance. All Smalltalkers should own this book, and programmers in other languages can probably find a lot of inspiration too.
SBPP shed a new light on my previous knowledge of "patterns" in computer programming. I was deep in the DP tar pit. SBPP saved me. Read more