Object-Oriented Thought Process, The (Developer's Library)

I've been writing code for awhile now and every few years like to go back to the very, very basics since it's easy to lose little details here and there. I feel like going back to the fundamentals helps keep me sharp, but, given my experience level, I don't need a dense textbook.The Object-Oriented Thought Process is a book I come back to time and again despite the fact it feels dated (partially due to the talk about Smalltalk...). You get a great overview of the concept of objects vs structured programming (which is the tide OOP was fighting against at the beginning), SOLID, a high overview of design patterns, etc. There are mainly Java-based examples throughout the book.If you're new to the field, The Object-Oriented Thought Process is a great way to get yourself acquainted with the fundamentals behind virtually all OOP languages. If you've been around awhile and just want to make sure you have all the details fresh in mind, you'll find The Object-Oriented Thought Process is a breezy read that gives you just enough information to bring up the old memories.

This books is a very gentle introduction to OOP/OOD from a conceptual standpoint. Although the book uses Java (for obvious reason) for code demonstration, it doesn't intend to teach you how to do OOP in Java OR doesn't expect you to know any Java. The concepts are explained very clearly. On some occasions you will see some concepts are introduced that might not seem to perfectly fit into the conceptual progression of the book, but that's usually momentary and if you proceed with your reading soon you will see everything falling in place at the end. So there is a general plan to the whole book and the structure of the book follows that plan almost perfectly.When you finish this book you will be completely conformable with OOP concepts and if you pick up a book let's say on OOP in Python you will not be discouraged when you encounter concepts like "multiple inheritance", "constructors' , "object wrapper", "contract", "cardinality", "factory method" or "SOLID". In general I think the book is very conceptually clear and to be honest an interesting read. An alternative to get what this book is teaching you would be to go and learn a so-called pure object oriented language like SmallTalk or Java (close-enough) to get how OOP/OOD works in practice, but considering how much time that would take it doesn't seem like a very practical for many people who just want to know what OO is really all about. So in that regard this book is one of kind and I definitely recommend this to people with little or no background in the Object-oriented way of thinking in programming.

I wish I could give this book 4-5 stars because there is so much great material about OOP, and the author does a great job of breaking down the concepts into their essence. Sadly, it seems as if the 5th edition wasn't properly edited and reviewed before publication because there are major typos and errors throughout every chapter. Sometimes, these are so bad that you have to reread passages multiple times to understand what the author is trying to convey. It appears that class/method/variable names must have changed between editions because often, the code samples and text descriptions won't line up at all.Luckily, I bought this book to review OOP, not learn the concepts for the first time, so I could still get a lot out of this book. If you're experienced, the typos and errors are all obvious enough to work around (although very annoying). If you're a beginner, I would advise choosing a different book, as the errors may make the concepts seem more confusing than they should be. It's a shame because the author seems really solid, but the editing is so poor.This is the only book I own from this publisher, so I'm curious if it's an outlier or more indicative of the kind of work the company produces. I'll definitely update this review if I purchase anything else from them.

This book is for those who wants to understand the main concepts of Object Oriented Design, rather than focusing on the syntax of a specific programming language

This is a classic OOP manual, written from the perspective of a problem solver

I loved the third edition, and this fifth edition is even better (and slightly shorter, a sign of improved treatment of difficult concepts). Still a classic and a must-read for any serious programmer.

Lots of sloppy typos in the code snippets. Notice in photo that comments are the reverse of what they should be. This is not a lone example.It was all very disruptive to the reading process. Shame because I waited a long time for this book (its publication date kept on being pushed back - so they certainly had time to proofread more carefully). Also a shame because the core text itself is good, which makes these errors all the more glaring.

$40 for this book is $35 too much. It's not entirely useless, hence two stars instead of one, but I would never recommend this book to anyone. A lot of the examples in the book, especially toward the end, use public attributes, which is textbook bad OO -- the book is awfully thin as it is, so there's no good excuse for trying to be concise. The book includes three design pattern examples and two of them are terrible, if not ojectively wrong (the MVC example oversimplifies way too much, such that most people would walk away with an incorrect understanding of MVC and the iterator example falls somewhere between missing and wrong). The author introduces SOLID design principles and references a youtube video!? Then goes on to describe SRP in the exact manner that Robert Martin has said that people frequently misunderstand SRP. The fact that this book is in it's fifth edition and has so many mistakes makes me think this author is a lazy grifter trying to make money without passing on sufficient value to the reader.