Hard to do when you are reading a book on Design Patterns, and you are 
> trying to understand one of the examples. I'm also currently reading 
> the same book as RichardOnRails, but I'm not quite that far along.
I've read the book. It's good but I think it's healthy to understand how design patterns aren't always necessary in Ruby like they are in Java. I'm just pointing out other, potentially more effective ways to write re-usable code.

Cheers,
David