- Series: Developer Reference
- Paperback: 368 pages
- Publisher: Microsoft Press (February 21, 2004)
- Language: English
- ISBN-10: 0735619654
- ISBN-13: 978-0735619654
- Product Dimensions: 7.3 x 0.9 x 8.9 inches
- Shipping Weight: 1.6 pounds (View shipping rates and policies)
- Average Customer Review: 26 customer reviews
- Amazon Best Sellers Rank: #971,464 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Object Thinking (Developer Reference)
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
About the Author
Dave West would like to describe himself as sheik geek. Unfortunately no one else would describe him in that way. They would say he is a professional Englishman who likes to talk about software development best practices with the passion and energy of an evangelical preacher. Recently Dave has moved to Ivar Jacobson Consulting, where he runs the Americas and can combine his desire to talk about software development and spread the word on rugby and football, and argue that cricket is more exciting that baseball. Before running the Americas for Ivar Jacobson Consulting, Dave worked for a number of years at Rational Software (now a part of IBM). Dave held many positions at Rational and then IBM, including Product Manager for RUP where he introduced the idea of process plug-ins and agility to RUP. Dave still laments the days when he use to sit in a cube and write software in the city of London. This is where he believes he cut his teeth writing big insurance systems with nothing but a green screen and a process flow chart.
Dave can be contacted at firstname.lastname@example.org, and if he is not with customers or drinking warm beer with his friends in Boston, he will email you back.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
* The first few chapters help the reader understand between the culture difference between 2 camps of 'scientific logical method-driven designers' and 'heuristics-driven artistic social designers'.
* Chapter 3 outlines the 4 fundamental tenets of object oriented thinking.
* Chapters 4 n 5 throw some light on the terminology and subtle thinking differences.
* Chapter 6,7,8,9 are the 'How-to'/actionable chapters.
* Chapter 10 is just bizarre... disjointed
The book as a whole doesn't exhibit 'flow'... something feels off. The book also doesn't promote lucid language frequenty throwing in important sounding words :)
The book definitely could have been shorter to make a better impact- I liked a bunch of ideas like Object Cubes (an extension to the CRC Card) as a thinking tool (I don't think I'll be building any physical cubes), the 4 presuppositions of object thinking, 'All inheritance must be based on behavior extensions', the little 'Behind The Quotes' sidebars , 'Object as a person' metaphor. Self-evaluating rules, Event Dispatchers and the DataItem type (as opposed to passive data) are interesting. That said it is a refreshing (though opinionated) change to read about the craft behind OOP. 4 out of 5 stars.
#1: if you are looking for specific, concrete advice (other than at a very general level) on how to construct objects, look elsewhere. The closest thing to concrete advice I could find is that the ratio of comments in your code should approach 0%, and that any system should be expressible using a maximum if about 1,000 classes. These may be valid guidelines, but I was expecting more about, to pick one example, whether classes should call their own getters/setters. Also, he kind of glosses over what is, IMO, the #1 issue in commercial programming and OOP: the DB impedance mismatch. He does mention this but never really deals with it.
#2: this book is, as usual, loaded with unsubstantiated claims about how, basically, all software productivity problems would be solved if only all the unwashed ignorant masses were to adopt the author's theories about how to think about OOP. This is ironic as the book frequently quotes Robert Glass, whose book I found to be the opposite in this aspect (eg. Glass had lots of data to back up his claims, as did, IIRC, Code Complete; though that one has been a while).