The Object-Oriented Thought Process (3rd Edition

The Object-Oriented Thought Process (3rd Edition
Matt Weisfeld
04 Sep 2008
Purchase online

The Object-Oriented Thought ProcessThird EditionMatt WeisfeldAn introduction to object-oriented concepts for developers looking to master modern application practices.Object-oriented programming (OOP) is the foundation of modern programming languages, including C++, Java, C#, and Visual Basic .NET.

Page 2 of 2
  1. Editorial Reviews
  2. Customer Reviews

Customer Reviews

P. Dimitrios said
1.The whole book could have been written in 20-30 pages. Really!

2. Now if you dont know anything about OOP, I think books that to explain concepts through ballons which have properties (red/blue/plastic) states(IsBlown) methods(BallonFly,BallonMakeNoise) events(OnBallonNail,OnBallonTouch) and other "abstract" manners DO HARM the reader. The beginner is left with a big ?, bigger than if he wouldn't red anything about OOP.

3. On the other hand if you know OOP the hard way, by experience through languages, this book HAS NOTHING TO OFFER, except maybe one ot two refreshing concepts.

Tony the Tiger said
I've had this book at home for many years (1st ed.) and I recently picked it up and read it. It is a very good working introduction to OOP. It's relatively easy to read, not dull, provides good examples of the ideas, uses a little java (which you don't need to be an expert on. I'm mostly a SAS programmer), and it covers some UML. I will certainly try to keep these concepts in mind when I later attempt to create a web application programmed with PHP.

j-bone said
I don't have the money or time to go to school for computer science. So, you can imagine how grateful I am when I find a good teacher through the pages of a book. My primary interest is web design (imagine that), and more specifically cakePHP. Since cakePHP is an object oriented framework, it stands to reason that I should understand what is going on under the hood from an OO perspective.

I've only read the first two chapters so far, but already I am beginning to grasp why the model, view, and controller classes are designed the way they are and how to extend them. I am beginning to have a better understanding of the algorithms I write and their place inside a class proper. I also helps me understand cakePHP as an OO driven framework.

One commentator made the statement about grasping the importance of thinking in terms of state, rather than structure, and that perspective has made a world of difference. It's similar to learning the order of operations (PEMDAS) is the thread that ties algebra and calculus together. Things just make sense, at least for now.

I recommend this book to those of you who are driven to learn on your own. Add this author's name to your list of 'professors' for future reference.


Blake E. Burnworth said
I am a longtime developer who wanted a deeper understanding of the fundamentals of OO design. This book definitely provided that. I understand the underpinnings of what I am doing when working with existing objects and can now design GOOD classes on my own.

The only complaint I have (and this is true with many books) is that the examples are not the type of thing you would come across in the course of writing an application. The cabbie example was great for getting across the IDEA of how incapsulation or inheritance work but I would like to have seen something more concrete like a Data Access or Company class. Still a great book though.

F. Tzanabetis said
Decided to have a look at this book to see if it's fit for some colleagues who are unfamiliar with OO.

I'm up to chapter 6 of this book and so far it's not a bad introduction to OO concepts, but in chapter 5 under "Keeping the scope as small as possible" it states -

"Static attributes and methods are shared among objects of the same class; however, they are not available to objects not of the class"

Err, sorry - FAIL!

What absolute hogwash. public static members of a class can be accessed from anywhere, including from objects not of the class. This is a fundamentally wrong statement. Unless I'm reading it wrong?

You might also like...



Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.” - Donald Knuth