![]() Trade In this Item for up to £7.90
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Smalltalk Best Practice Patterns for an Amazon.co.uk gift card of up to £7.90, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details
|
Smalltalk programmers, project managers, teachers and students -- both new and experienced.
This book presents a set of patterns that organize all the informal experience successful Smalltalk programmers have learned the hard way. Understand these patterns, and you can write much more effective code.
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
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).
|