Hal Fulton wrote:
> Picklegnome wrote:
> 
> [snip]
> 
>> useful. However, I am befuddled by much of the code that I read. While 
>> it is
>> possible that I am simply not proficient at algorithm design and am 
>> unable
>> to follow algorithms that are designed by others, I suspect that it is 
>> more
>> deeply rooted in my lack of "getting" OO.
>>
>> I've got no idea what resources might be used to overcome this 
>> problem, and
>> I am not even certain of my diagnosis. However, I would appreciate any
>> suggestions, resources, or help that you could offer me, because I am
>> excited about Ruby and eager to get past this blockage.
> 
> 
> Hmm, I could refer you to chapter 1 of _The Ruby Way_ (soon to be in
> a 2nd edition). But read it in the library first, don't spend your money
> on something you might not use.
> 
> Chapter 1 of Damian Conway's _Object Oriented Perl_ is also good.
> 
> I also enjoyed the discussion in Bertrand Meyer's book _Object Oriented
> Software Construction_. That's where I learned OO myself in 1990.


I liked Rebecca Wirfs-Brock's Designing Object-Oriented Software.  It 
does a good job of explaining how to think about objects in terms of 
roles, responsibility, and collaboration.

http://www.wirfs-brock.com/DesignBooks.html

It tends to be kinda pricey, so add it to your library list.  (But buy 
Hal's book when the new edition comes out.)


-- 
James Britt

"In Ruby, no one cares who your parents were, all they care
  about is if you know  what you are talking about."
   - Logan Capaldo