Most Programmers Dont Grok Objects

Just a couple of datapoints based on personal experience:

-- StevenNewton


I was training two inexperienced C++ programmers (who, effectively, only knew C)... One who wanted to learn, and the other who really didn't seem to want to be bothered.

From the one who didn't want to be bothered: The other was more interested in learning, and we made a lot of progress. -- JeffGrigg

Confused by the COM example. What was he calling QueryInterface on, if not an object he got through some other route?


So how did we come to grok objects?

See HowiLearnedToLoveObjects
Noun Vs. Verb Abstraction

Re: "At the same job I tried to mentor a co-worker moving to OO. He never did get it -- he didn't see anything as abstractions, everything was procedural/functional in his world view."
OOP and Code Size

Re: "Based on some Java servlet code I recently worked on (read: followed up after the initial programmer moved on to another job) some VB-style programming habits seem to have become associated with OO. The code was event-driven, and the 'objects' were all in the respond-to-this-event-do-something model. Which is OK except that every event was handled in isolation, even though there was really a great deal of commonality of function across the dozen or so 'events'. A straightforward candidate for CommandPattern, but generally each source file was a poster child for CopyAndPasteProgramming."
See also: ObjectOrientedDesignIsDifficult


EditText of this page (last edited January 1, 2009) or FindPage with title or text search