This post originated from an RSS feed registered with Ruby Buzz
by Adam Green.
Original Post: Programming for a tutorial
Feed Title: ruby.darwinianweb.com
Feed URL: http://www.nemesis-one.com/rss.xml
Feed Description: Adam Green's Ruby development site
I'm still getting great emails from people welcoming me to Ruby, but there seems to be a bit of confusion over my goals with this RubyRiver code. It is meant to be the basis of a tutorial for new Ruby programmers, and possibly people new to OOP. Writing code for new programmers means that the tightest, most terse methods are not always best. I appreciate all the suggestions for making the code shorter, or using regular expressions, or classes, but please don't be disappointed if I don't follow them for a while. Sometimes four or five lines of code are actually easier to read than one. The first version of the code will be procedural, so I have something to convert to OOP later. The tricky part is that I am learning as I go, so I don't know the best techniques either. I do know that after a year or two it will be hard to remember what was confusing, so there is value in writing about it now while things are still fresh.
Previous Topic
