- 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 9.1 inches
- Shipping Weight: 1.6 pounds (View shipping rates and policies)
- Average Customer Review: 26 customer reviews
- Amazon Best Sellers Rank: #276,990 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.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
"Rebound" by Kwame Alexander
Don't miss best-selling author Kwame Alexander's "Rebound," a new companion novel to his Newbery Award-winner, "The Crossover,"" illustrated with striking graphic novel panels. Pre-order today
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
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.
Author interviews, book reviews, editors picks, and more. Read it now
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.
Whenever someone tells you, "you have to experience this to understand why it's so great", that's a tip off that he has no strong objective evidence to support his position, and that his attachment to the concept is emotional in nature. Despite his assertions, it's quite possible to do highly effective software development without XP, and I've seen projects that were wholly XP-oriented that were massive failures. So I'm not particularly sympathetic to XP evangelists to start with. (I don't mean to imply that XP is useless. But's it's just one methodology choice among many, and there's nothing special about its success rate.)
But sneaking in XP evangelism under the guise of talking about object orientation is downright disingenuous. Object oriented concepts don't have anything do to with extreme programming, and the author's forced efforts to connect the two are quite lame.
I wish it were otherwise. We need a good recent book on object oriented concepts (as opposed to object oriented syntax). I think this could have been that book, if the author had resisted the urge to evangelize instead of instruct.