56 of 58 people found the following review helpful
A Rails 3.0 reference for experts, but a flawed champ..,
This review is from: The Rails 3 Way (2nd Edition) (Addison-Wesley Professional Ruby Series) (Paperback)
The Rails 3 Way is an interesting book representing a large amount of effort digging into Rails 3. It shares insights and technical knowledge you'd struggle to patch together from blog posts and documentation. It's a very opinionated book and will not be to everyone's taste. For starters, ERb isn't covered at all, instance variables in views are scowled at, and Test::Unit is treated with contempt.
It's not an introductory book in any sense and Obie acknowledges this in his introduction. Obie bills it as a "day-to-day reference for the full-time Rails developer" - a fair description IMHO, but the book feels disjointed in places and has a scattershot approach to what it cares to cover. You need to be clued up to digest this book properly. For an intermediate to expert Rails developer (especially one yet to move to Rails 3) or an expert Rubyist new to Rails, The Rails 3 Way is a useful book that unearths some of the trickier parts of Rails 3 a professional needs to know about. I recommend it - but not as wholeheartedly as the original edition for a number of reasons:
* Parts of the book feel curiously short or scattershot in their coverage. The AJAX on Rails chapter is a mere 16 pages. The RSpec chapter is 33 pages long and provides only an overview (and says as much) though given the recent release of RSpec 2.0 and the new RSpec book, this may be a plus. Rails Engines aren't discussed or covered at all except for a small sidenote that links you to a gist on GitHub. It's not all bad though - some chapters are great, complete guides to a topic, such as Active Record Associations and Advanced Active Record.
* A lot can be gathered from what's not mentioned in the book at all: Capybara, Selenium, Webrat, Searchlogic, SASS, factory_girl.. It wouldn't be expected for a book like The Rails 3 Way to go into depth with any of these tools but having no mentions of them when related issues are raised feels like a missed opportunity to give people some guidance. The lack of Webrat is bizarre since the only full integration test shown in the book clearly uses it. Webrat is neither mentioned nor explained. Nor is Capybara, Webrat's heir apparent.
* The concept of using a different ORM than ActiveRecord is mentioned only once, in the context of running --skip-migration on a rails generate in order to prevent ActiveRecord migrations being generated. Considering what a big deal ORM agnosticism was when developing Rails 3, this is a disappointment.
* Concepts are sometimes used in code but not mentioned in the text. In the RSpec chapter, for instance, the first example includes a call to factory_girl's Factory method, yet nothing about factory_girl or the benefits of factories is covered. I only know it's factory_girl being called because the gem's name appears in the copy-and-pasted output from running bundle install 500 pages earlier.
* Tests are rarely used or demonstrated except in the RSpec overview, Working With Active Record (4 test snippets in 39 pages), Action Mailer (once), and Active Record Associations (6 test snippets in 50 pages). Oddly, though, 4 stray instances of using Test::Unit instead pop up when writing a test for a belongs_to association - it's never used again anywhere else in the main part of the book..
Nonetheless, I recommend the book. It's a flawed champ. While there are other great Rails books in the pipeline, The Rails 3 Way offers a lot right now, as long as you're either happy to look past its flaws or skilled enough to mentally fill in the blanks..
Tracked by 4 customers
Sort: Oldest first | Newest first
Showing 1-9 of 9 posts in this discussion
Initial post: Dec 19, 2010 11:44:14 PM PST
Scott Mueller says:
Sounds like a 4-star review, did the author get a bonus star for being a friend?
In reply to an earlier post on Dec 20, 2010 12:11:53 AM PST
Last edited by the author on Dec 20, 2010 12:16:11 AM PST
I wouldn't go as far as "friend." I've had contact with Obie a handful of times over 4 years and, to be fair, I'm not sure he's ever done anything for me ;-) He is someone I am "friendly" with, I guess.
It's more the Author's Code. I like to keep the nice. While I'm fair and balanced in my review for those who choose to read it, star ratings on Amazon have a big enough effect on rankings here that the 5 is the pragmatic, if generous, option. It's a little white 1 star-difference lie. FWIW, Obie didn't even ask me to review the book (and I suspect he won't ever do so in future.. ;-)).
In reply to an earlier post on Dec 29, 2010 4:01:30 PM PST
Rafael Sorto says:
Would you please expand in the "..Rails books in the pipeline.." and mention a couple of them ?
In reply to an earlier post on Dec 31, 2010 10:58:43 AM PST
Matthew A. Blair says:
Peter is probably referring to Rails 3 in a Nutshell: A Desktop Quick Reference and Manning's Rails 3 in Action by Yehuda Katz and Ryan Bigg, which isn't listed on Amazon.com yet.
In reply to an earlier post on Dec 31, 2010 6:07:34 PM PST
"Crafting Rails Applications: Expert Practices for Everyday Rails Development" by José Valim is one that stands out in particular.
Posted on Jan 7, 2011 11:26:20 AM PST
Amazon Customer says:
Which Rspec 2.0 book are you referring to?
In reply to an earlier post on Jan 7, 2011 11:35:11 AM PST
"The RSpec Book: Behaviour-Driven Development with RSpec, Cucumber, and Friends" by David Chelimsky, Dave Astels, Zach Dennis, Aslak Hellesøy, Bryan Helmkamp, Dan North.
Posted on May 15, 2011 8:06:56 PM PDT
Ryan. S says:
This isn't a 5 star review. You're fudging the review rankings.
In reply to an earlier post on May 16, 2011 3:55:58 AM PDT
Star ratings are worthless. A couple of "wrong" ratings from reviewers who've missed the point can seriously damage a book's reputation on Amazon. So I tend to give everything 5 (unless it's really bad) and then let my review do the talking. Anyone who buys solely on star ratings rather than the content of the review isn't doing enough research.
‹ Previous 1 Next ›