2009/12/9 Vahagn Hayrapetyan <vah...@gmail.com
> Hi Johannes,-
> that's an interesting recipe for getting better at Rails - I assume you were
> already proficient at Ruby before reading the Rails source? I tried doing
> that before I had any real Ruby literacy (I was coming from the Java / .NET
> world), and found it to be challenging.
> I'm getting better at Ruby idioms now, so at some point I'll definitely
> follow your example. One has to get past the point of "syntactic haze", when
> one stares at the code figuring out what the syntax means as opposed to what
> the program does.
Yes, I had done some Rails development at the time. In fact, I got to
it by accident - I though I had discovered a bug and did look for a
better information on the ticket (it wasn't a bug ad all :D).
But I think, starting to read the code of any application is kind of
hard. At first, you don't understand anything and I had the impression
sometimes, that it doesn't change. But after some effort, I got some
clue and after another, it even starts to get easy.
By the way. Dave Thomas has given a great interview about reading code
to SE-Radio: http://se-radio.net/podcast/2009-11/episode-148-software-archaeology-dave-thomas