For a while now, I’ve been interested in dynamic languages – especially the metaprogramming capability. I’ve dabbled a little in Python – largely out of interest in Django – but a lasting relationship hasn’t formed. So, I figure it’s time to try Ruby properly. Here’s the plan:
Read one or two good books
I’ve ordered The Ruby Programming Language, which has already arrived, and The Ruby Way, which hasn’t. So far, I’ve got a fewty pages into the first book, which seems like a good place to start and will I think, become a useful reference.
Subscribe to a few blogs
Books are all well and good, but there’s nothing like a blog for connecting to the latest developments, ruminations and general goings on in the Ruby community. Having done a brief scout about the blogosphere wearing Ruby coloured glasses, I’ve subscribed to the following:
Ruby Inside – so chock-full of Rubyness that if there were a place called Rubyville and it had a daily newspaper then this might be it.
Ruby Flow – Ruby Inside’s sister is a community-driven, Ruby focussed link blog.
rubydoes.net – all things IronRuby collected into one handy, easy-to-read blog.
John Lam on Software – it’s written by John Lam and it’s about software, what more could you want?
Jimmy.Thinking – more Silverlit IronRuby information and thoughtfulness.
Try some stuff
There’s not much point in learning Ruby unless you use it to do something. I don’t have some fiendish plan to build anything specific, but I want to include IronRuby in my programmatic doodlings.
To maintain some momentum, I’m aiming to post about my progress and experience every week – on Tuesdays. Which makes this post the first in the Ruby Tuesday series. Any feedback, help, tips and so forth are, of course, greatly appreciated.