Most helpful critical review
7 of 8 people found the following review helpful
Too few recipes are worthwhile reading
on March 4, 2013
The author focuses largely on what can theoretically be done within Rails and not on what should be done in a real world application. A good 20% of these recipes are already well documented practices that are already listed on the current RubyOnRails.org. Worse though there are too many recipes that are borderline dangerous, violating fundamental design principles such as S.O.L.I.D, Law of Demeter and the Principle of Least Surprise.
Many recipes highlight their "advantages" only in form of improved readability. Downsides of recipes are almost never mentioned, creating the impression to the novice programmer that each and every one of them is a good idea. Unfortunately the consequences of what happens under the hood in terms of disk seeks, memory and CPU are entirely missing, leaving the reader guessing on how to make intelligent engineering tradeoffs.
I personally recommend reading the "Database Recipes" chapter, as well as the following 6 recipes:
- Create custom form builder
- Test your outgoing Mailers
- Test across multiple controllers
- Create test data with factories
- Automate work with Rake tasks
- Debug and Explore your application with the ruby-debug gem
All in all, out of the 70 recipes there are too few worthwhile reading.