- 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: 3.7 out of 5 stars See all reviews (27 customer reviews)
Amazon Best Sellers Rank:
#478,717 in Books (See Top 100 in Books)
- #154 in Books > Textbooks > Computer Science > Object-Oriented Software Design
- #179 in Books > Computers & Technology > Networking & Cloud Computing > Data in the Enterprise > Client-Server Systems
- #517 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Object-Oriented Design
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.
Prepare for your professional certification with study guides and exam prep tools from Wiley. See more
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 email@example.com, and if he is not with customers or drinking warm beer with his friends in Boston, he will email you back.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
However persevere, because it's worth it! Although the language and presentation is almost the polar opposite of one of the "companion" titles in this series ("Extreme Programming Adventures in C#") this has a very high signal to noise ratio (which sadly the other much fatter volume doesn't!). So, don't be put off by the long names and endless footnote references to old ACM papers because what's presented here is a thoughtful and convincing book on the history of object-oriented development, the politics and design errors that have caused the "wrong" thinking to take place and a convincing argument as to why so many of us have got object orientation so wrong. The blurb promises "visionary insight" and if you can get through some of the "academic" language, against all expectations the book delivers on that promise. This ISN'T, as you might expect from a Microsoft Press book, a book of code examples and "silver bullet" handbook for the developer who wants to cut and paste code, for reasons that are well explained in the book. It IS a great guide to why current thinking is often wrong and what you, as a developer, need to do to develop your "object thinking" and deliver on the promises that have been made in its name.
Frankly I'm amazed and encouraged to see such a great "agnostic" (where Microsoft technologies are concerned) book published by Microsoft Press. This is one of the best titles I've read (and I've read a lot!) in their extensive catalogue. Perhaps the most important advice is that "Object thinking is hard", as the book's author professes, and while there aren't any "silver bullets" this book does guide you through a difficult path that will help you "think objects" and produce better solutions.
I award this book 3 stars, because I feel it is extremely repetitious, making the same point over and over again; it could easily be trimmed down to half its size, if not more. Also, it is not an easy read, using many technical terms thrown in unneccessarily (IMHO). I feel that with extensive restructuring of the content, it could become a book worthy of its content.
* 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.