Ruby Tuesday #4 : Time to Productivity
So far I’ve concentrated on setting up an environment. Meantime, I’ve been reading about Ruby and trying to learn the syntax. It’s at this point that you wonder if you can ever be productive in the new language. The syntax is relatively easy – it’s the rest that is more daunting. The rest is the stuff you take for granted in your preferred language, stuff like how to organise and layout files, how to deploy, what’s in the standard libraries, etc. It’s like learning a new language: despite a grasp of the grammatical rules, all you can say is “Where might I find the nearest tractor repair shop?” – and you don’t quite understand the response. This wouldn’t be an issue if you weren’t already proficient in a language because you wouldn’t know how much more you could achieve.
So, the question is how long does it take to become productive and how best to go about learning the real stuff. From past experience of learning new programming languages, the answer seems to be build something – in addition to continuing to read as much as possible. What should that something be?