While this is an interesting case (having done the Treehouse tutorial myself), I've got to say that you can't beat Michael Hartl's book for a decent intro to working with Rails.
It's good to read bits and pieces here and there, but he deviates too much into Git, Github, Heroku, Unit Testing, etc.
I want to learn Rails and Ruby. An already hard enough task.
There's no reason to smash my face into so many new concepts at once.
-Source: Myself when I starting out with Rails.
A much better source I found is the book Agile Web Development with Rails from Pragmatic Programmer Bookshelf:
http://pragprog.com/book/rails4/agile-web-development-with-r...
Starts with dumb, .html.erb files, for static HTML, then slowly builds up on previous lessons - WITHOUT GOING TOO MUCH OFF TANGENT.
Unit tests, rspec! the second coming! yada yada. I wanted to learn Rails, most newbie want that as well.
One must work hard to grasp what is being taught. It requires a lot of motivation, reviewing and double checking. Too much is given at once, in the wrong order and with little explanation (if any). Too much is left open. Proper subject matter review for a consistent explanation isn't available.There is a summary at the end of each chapter, but it is as a statement of goals "achieved" and not an explanation. I could list many examples. One can easily get lost following (or trying to follow...) the book. It can be a real pain.