Smalltalk Best Practice Patterns

A foundational text cosplaying as a niche guide. The patterns within are fundamental principles of software design, relevant to anyone using C++, Java, C#, Python, Ruby, JavaScript, Rust, or even Agda and Idris. This book's explanation of the Composed Method pattern is arguably one of the most important lessons a programmer can learn. It teaches you to break down complex logic into small, well-named, single-purpose methods. This is the core of writing code that explains itself. You do not need to know or learn Smalltalk to get immense value from this book. If you work in an object-oriented language, this book is non-negotiable in my opinion. It sidesteps transient fads and focuses on the evergreen principles. There is a reason there isn't a 2nd Edition of this book that uses Java; it was not necessary. As I write this I am finishing my 28th year as a professional software engineer.

Kent Beck is always on point and this book explains patterns in a way that I understand them. The book is in the condition the seller said it would be so no surprises there. It even showed up a day early.

This book is mostly about object oriented programming and the Smalltalk programming language. It does have some good stuff about the basics that every programmer should know. Having a good foundation before starting a coding project is important, and this book is great for that. Nothing ground breaking here, but still pretty good for beginners who have never learned how to structure their code.

this is one of the books that I reach for all the time. I use it to explain many concepts and I don't even write smalltalk. I have a hard copy and digital. I've also given a copy away as a gift. this is a must have when trying to build a common vernacular. It has improved communication of ideas for every team I've worked with.

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.

Although not a recent book, it gives a great overview of sound object oriented coding practices. At the same time it is an excellent showcase of the beauty of Smalltalk.

This book is great for learning design patterns even if you don't know smalltalk. This is a must read for developers.

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!

Wer effektiv in Smalltalk entwickeln will muß sich dieses Buch (mindestens) einmal durchgelesen haben, aber dannach gibt man das Buch sowieso nicht wieder heraus. Auch wenn ich viel in Java entwickle, so kann ich behaupten dass mich der Smalltalk Exkurs verbessert hat. Auch wenn Smalltalk nicht die Zielsprache ist, so lohnt es sich auf jeden Fall sich in dieses Buch reinzuarbeiten.

Great advice applicable today but recommended only for people who can look past the smalltalk syntax, so probably at least a few years of programming.

but also for polymorphic messages and object-oriented programs in general. The book is worth it for not only the short, succinct code examples, where Smalltalk really shines, but also for the preface and introduction, which goes straight to the point, how perception of programming and its role shapes how you think about and approach the activity of programming. I have found its examples useful not only in the context of other object-oriented programming languages, but even for programming languages in other paradigms, and programming in general. It is not just about "low-level design" or programming idioms, but how you think about your day-to-day activities in programming. It does this without becoming philosophical, and instead does it by showing code examples with just enough explanation to get an understanding of the rest. I have found it much better the later book "Implementation Patterns" by the same author, which is just a lexicon of low-level idioms, which any programmer knows by heart, i.e. by doing, and doesn't stir the reflexions of the art of programming that this book does. It is difficult to pin-point the significant difference between the two books, but this one seems more pure hearted, not afraid, neither conventional nor industrial or dry, more fun, and coherent like a hard diamond in language, style, and examples. It is simply beautiful without being fashionable or flashy. While being a lexicon, it is more like a great disposition of small articles where the organization is as important as the content, and it has some of that flavor that the old Basic introductions of the 1980'ies had, the flavor of curiosity, fun, inspiration, and it leads by example and encouragement rather than dictating and advising in a misguided professional tone that so many other books do. It reminded why programming is enjoyable when you leave out everything else that doesn't add to its fullfillment and satisfaction.

Aunque se trate de un libro sobre Smalltalk, sus consejos son válidos en otros lenguajes "más modernos". Además la sintaxis de smalltalk permite que los ejemplos puedan mostrar la esencia del principio que ilustran.

I'm an Objective C developer, and as you know Objective C derives a lot from Smalltalk culture, including syntax. This book helped me a lot in class design, better code reuse. Some of the chapters are not applicable though, since Cocoa (Touch) provides different means for dealing with arrays, etc. But anyway. If you're going to become a (much) better class designer, this book will help a lot. Even if your language of choice stands well away from Smalltalk.