ACCU Home page ACCU Conference Page
Search   Contact us ACCU at Flickr ACCU at GitHib ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

ACCU Menu

Advertisement

Advertisement

Membership

Join ACCU

Login

» Create an account

» Password Reminder

ACCU Buttons

Add them to your site:

ACCU: professionalism in programming (116x31 px)
ACCU: professionalism in programming (225x60 px)

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1949 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
The Object Oriented Thought Process
Author:
Matt Weisfeld
ISBN:
0 672 31853 9
Publisher:
Sams
Pages:
226pp
Price:
£21-99
Reviewer:
Francis Glassborow
Subject:
object oriented
Appeared in:
12-5
There are two fundamentally distinct ways to learn about OOP. The first is to study a computing language that either supports OOP (such as C++) or requires it (Smalltalk). The second is to study OOP in and of itself and then later learn a computing language in which you can apply the understanding that you have gained.

This book attempts to find a third way by setting out to teach you about the general thought processes that lead to OO code while using snippets of code written in Java to communicate the ideas. I think this is fundamentally flawed. If you are to acquire solid OO thought processes then this must be done out of the context of a computing language. The fact that the author finds this a step to far suggests to me that his grasp of OO is still a little less than confident.

There is a considerable amount of merit in this book, but, in my opinion, it is not yet ready for publication.

What have such things as deep versus shallow copies to do with the fundamentals of OO? It is things like that which lead me to think that the author is reasonably familiar with OOP in C++ and Java but has not succeeded in abstracting his understanding from the languages he is using.

In simple terms there is too much language implementation detail for a book with this title. This is not a bad book, just one that does not achieve what it claims.