Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen learning Ruby on Rails, should I focus on just learning Rails or learn associated technologies along with it?
    text
    copied!<p>I'm planning on taking the time to actually learn Ruby on Rails in-depth (I've previously done some very minor dabbling with it) so I can hopefully reinvent myself as a Rails developer.</p> <p>The issue I run into though is that there are a fair bit of related technologies that are currently used in the Rails community, and I'm not sure if I should learn the whole shebang or focus on learning Rails with the defaults first, and then branch out into the additional stuff.</p> <p>For example:</p> <ul> <li>Templates. I took a look at <strong>Haml</strong> and it looks really cool (shouldn't be hard to learn either).</li> <li>Testing. I've wanted to learn test driven development for a while now, but the "next big thing" in Rails-land seems to be behavior driven development with <strong>RSpec</strong></li> <li>Javascript. I'm not sure if I should stick with <strong>RJS</strong> or use something like <strong>jQuery</strong> which seems to be converting people.</li> <li>I've never really used version control much. Rails seems to be using <strong>Git</strong> for most of it's projects.</li> </ul> <p>Basically I want to learn Rails "right", but there seems to be a lot of different ways that I could go. Should I ignore the "variants" and focus on the Core stuff until I've written an application or three (e.g. core, unmodified Rails; RJS w/Prototype and Scriptaculous for Ajax, regular Test::Unit for testing, ERB for templating, Git for version control), or should I try to pick up some of the variants along the way?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload