Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>To become good at Rails in my opinion you should first be sure that you understand Ruby well. I would suggest browsing through (careful reading is not necessary if you're already an established programmer) some of the basic ruby books like: <a href="http://mislav.uniqpath.com/poignant-guide/book/" rel="nofollow" title="Why's Poignant Guide to Ruby">Why's Poignant Guide to Ruby</a> and <a href="http://www.ruby-doc.org/docs/ProgrammingRuby/" rel="nofollow" title="Programming Ruby">Programming Ruby</a>. </p> <p>After this, you should become familiar with the Rails API's and DSL's, I would suggest beginning with reading <a href="http://guides.rubyonrails.org/" rel="nofollow" title="Rails Guides">Ruby on Rails Guides</a>. When you understand the Rails basics the ultimate Rails reference is Ryan Bates' excellent <a href="http://railscasts.com/" rel="nofollow" title="Railscasts">Railscasts</a>. If you don't like watching videos the site has an <a href="http://asciicasts.com/" rel="nofollow" title="Asciicasts">ascii mirror</a>. Even if you don't have a specific task in mind, go watch a few of these to really understand the way problems are tackled in Rails.</p> <p>Ofcourse when it comes to actually gaining skill in developing Rails skills, it is imperative that you try your hand at actually making a few Rails applications. Rails has a notoriously steep learning curve, so it's best when you have tried a few simple unimportant applications before you try to build your life's work with Rails.</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