First Official Week of Rails
When I was in Seattle over the summer, I knew that coming back this fall I would have the opportunity to mess around with Rails. I had some upcoming projects and I could either code them up using systems I knew well (.net, php, django, etc.) or take a chance on the steep learning curve that is Rails. I had a couple of Pragmatic books shipped to me in Seattle, read over them on my endless commute to Redmond but never had the chance to sit down and properly code something.
I’ve been back in New York for two weeks. The first was spent figuring out Rails development environments, finally eating a good bagel, biking around the city, you know the important stuff. Starting this past Monday (it’s Friday now), i’ve manage to knock off half of my functional components list for a project. Half, with almost ZERO Rails coding experience as a starting point.
I’ve been able to code on my laptop without a network connection while waiting for street cleaning to be over (thanks Locomotive) and I am in love with migrations. Now I don’t think I know ruby that well yet, all I know is the rails way, well except for the fact that I still have no interest in writing tests. Old habits die hard. I also haven’t tried to do anything too interesting, everything I am doing is cookie cutter stuff. I’ve heard that’s when Rails gets difficult. It’s the Rails way or the highway and sometimes there isn’t a Rails way. Still, Rails is really dope. For example, the fact that a self-join is done through a concept and through the << operator is awesome.
That’s the update for now. Hopefully i’ll have the same attitude a few weeks from now.
