4 ms·
This is not a tutorial, and the title is supposed to be intriguing, not to be taken literally. Seems like you're pointing out the obvious, at least to me.
by michaelgrafl 14y ago
This is not a tutorial, and the title is supposed to be intriguing, not to be taken literally.
Seems like you're pointing out the obvious, at least to me.
- aarondf 14y agoMaybe it was obvious, but no one else had said it yet. I said it because I believed it would provide value to our community.
- michaelgrafl 14y agoYou're right. And I hope my comment didn't come across as harsh. I would have said the same thing to your face, but my tone and body language would have softened it quite a bit.
- ananthrk 14y agoAfter reading the article, even I found the title tongue in cheek. That said, GP has explicitly called out (quiet well) what he thought was the underlying lesson and I am thankful for that.
- dasil003 14y agoIt's a bit banal though, of course you should learn something valuable. Isn't that what your mother's been telling you all these years? I think the better lesson which is directly applicable to all coders is "question your assumptions". To me this was a huge benefit of learning ruby as it happens to be one of the easiest languages to pull your assumptions right out from under you.