Object Design Style Guide: Powerful techniques for creating flexible, readable, and maintainable object-oriented code in any OO language, from Python to PHP

Straight to business type of book. Author takes a topic, provides hints and tricks and explains why. No mambo-jumbo whatsoever. Great ratio of useful info per page.

This book should go hand in hand with other clean code, architecture books. You cant have write clean codes without the fundamental understanding of object design and guidelines. This book covers so many concepts and present real world examples in a concise manners. It doesn't matter if you are a well season software developer or a beginner. Maybe you simple want to develop an application that can be maintainable in the long run... Maybe you are a college student, This book is for you!!

I really hope this book gets another version, because the ideas about modern object design could be extremely helpful and enlightening. However, as it is, it reads like a rough draft of a hodgepodge reference book, and is the most dull technical book I've been exposed to in years.The book lacks a consistent principle based structure and uses overly abstract non-memorable examples and far too often uses simple "foo" and "bar" elements instead of illustrating real use cases. This is on contrast to a great book of this kind - Clean Architecture by legend Bob Martin, which pulls off a similar kind of thing, but much better.There is no "energy" to this book. No really informative motivating examples are given, and when they are, they are still so abstract to not warrant connections to real world examples. It is essentially a reference book and makes for extremely boring reading.The abstract structures of objects that demonstrate the lowest common-denominator of structure instead of memorable use-cases that would teach two things at once. This is appropriate in a few instances, but overall leads to unbelievably boring reading and makes it more difficult to remember.Also, the book is devoid of trade-off analysis and prefers dogmatic statements with occasional 'exceptions' that beg the question as to why one would truly prefer one structure over another. Sometimes standard design patterns that are very powerful are seemingly advised against ("Don't inject dependencies; optionally pass them as method arguments"), however in many circles, passing a dependency as an argument IS what dependency injection is, so why use some strange specialized definition?There are just so many issues like this. It needs another edition badly.The book has promise for its next edition, but this one seems to me to be nearly unreadable. I can tell the information in here would be gold if it was presented better, but for now, it takes every bit of willpower I have to slog through a few pages at a time to get its insights.

I searched C++ and found what I thought was a C++ Object book.This book was NOT what I needed.He uses a "fictional language" and it is eerily similar to C# and says that his fictional language uses null reference types. I believe that he thinks he is being as universal and accommodating but settle for a little vague.This book is targeted toward higher level programming language learners. If that is the case then I would pick up "C# in depth" by Jon Skeet. I would switch between that an a few other programming references.

After a few dozen pages my thought was "I like what Matthias posting in the blog but this is OOP extremism". Now that I've finished it I can say that this is very balanced set of advice.

Ho letto questo libro perché compreso nell'abbonamento annuale O'Reilly e trovandolo molto valido ho deciso che non doveva mancare come libro fisico. Il codice dii esempio è in PHP ma l'autore avrebbe potuto usare Java o Python senza nessun impatto sui concetti espressi. Manning si sta rivelando un editore sempre più di qualità.