Customer Reviews

Smalltalk Best Practice Patterns

5 star:		(18)
4 star:		(0)
3 star:		(0)
2 star:		(1)
1 star:		(0)

 

 

Although I've never used SmallTalk and have read only a couple of on-line introduction chapters on Dolphin SmallTalk, I had no problems reading it and applying the patterns in another language like Java, C++ or Python.

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!

Smalltalk Best Practice Patterns isn't just for Smalltalkers---there's something here for everyone who programs. Kent's insights, experiences, and raw wit are as entertaining as they are enlightening. If you have any passion for programming, in any language, buy this book. Read it. Live it.

Before I read Kent's book, my team had a Smalltalk coding guidelines document, a boring, cluncky text that didn't seem to help beginners write good code (mostly there so project quality plans could reference it). After I read Kent's book, I wrote a few team-specific points in the margins and declared it our new coding guidelines document.

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 bought this book years ago from McGraw-Hill in NYC,...but I'd gladly pay double...for it today - don't be fooled by the fact that there are only 240 pages to this small, softcover book. The patterns are concise and the examples, priceless. Although I love Gamma's Design Patterns, if I were forced to be stuck on an island with one choice, it'd easily be Beck's BPP.

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.

This is an excellent book that all Smalltalkers should have. This book should be helpful for beginners in avoiding common programming mistakes.

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.

I've never programmed in Smalltalk and probably never will. Actually, I'm not able to write the most primitive program in Smalltalk. Nonetheless, I highly recommend the book to anyone who has (or wants to develop) a sense for understandable and aesthetic code. Most of the advice applies to any programming language and even the parts specific to Smalltalk provide interesting food for thought.

This book should be adopted as a standard in all Smalltalk development shops. While many of the implementation patterns within seem obvious, the book can help solve the endless debates over which coding techniques to use and why. The book is useful to both novices and developers with considerable experience.

Idioms, patterns ... all programmers' minds should be imprinted with them. Why work hard, with these solutions at your fingertip?

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.

I wish more Java/C#/C++ programmers would read this (and maybe even learn Smalltalk) so that they can appreciate the weaknesses in those languages and possibly in their practices that they might not even realize today. I certainly did. While Robert Martin and others have offered up some of the canon of good design for contemporary developers, this little gem really reveals the "feel" of good OO.

SBPP has changed me. Kent Beck has changed me.

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. SBPP changed almost all my thoughts on programming. It has changed what I value, and how I pursue it.

Kent Beck says that he is not a great programmer but just a pretty good programmer with great habits. Build great habits with this book. Read and reread this book every morn.

If you have studied DP, this book will open your eyes to the wider world of patterns. You will think about DPs quite differently after this book. You will be able to escape from the bad effects of DP abuse.

If DPs were nouns, verbs and adverbs/adjectives, SBPP are articles and auxiliary verbs. SBPP are used much more frequently than DPs. When you learn a language it is very important to learn more frequently used words first. It could be less efficient(or even dangerous) to learn "appreciate" before "thank (you)".

--JuneKim