Bravo, James. I rarely have time to try the quizzes, but your tutorial 
summaries are outstanding.

This, in my opinion, is one thing we should do to increase Ruby's 
visibility: write articles and books that take the time to explain code 
in the context of a specific application and and strategy.

Self-documenting code is a myth. It tells you everything about the wasp 
but why [1-2].

Steve

[1] Semi-obscure literary references are no fun in the age of Google.
[2] 'why', not '_why'.