Rails recipes

What Hacker News says

1. melvinramJun 2012
   Rails Recipes and Advanced Rails Recipes

   http://pragprog.com/book/rr2/rails-recipes

   http://pragprog.com/book/fr_arr/advanced-rails-recipes

   The Advanced Rails Recipes is out of date but the concepts still apply.

   thread
2. carpalJan 2008
   1) I've never gotten much utility out of Rails books. I've generally gotten much more use out of the API docs and blogs. That said, the Agile Web Development with Rails book is pretty much standard, and Rails Recipes is good for code examples. However, if you're doing something in Rails Recipes, there's probably a plugin for it by now.

   2) Because it is very easy to implement an idea in a day and see if it sticks. More than that, when you're faced with a task that might not have much reward, it is easier to do if it doesn't feel like work. Programming in PHP/Java/C#/etc generally feels like work. Programming in Ruby generally feels like fun.

   Show morethread
3. jprobitailleMay 2007
   Books(In this order, if you know no Ruby): 1. Agile Web Development w Rails 2nd ed. It's available as a pdf direct from the Pragmatic Programmers

   -. Skip the Pickaxe book for now, the 1st edition is online at http://www.rubycentral.com/book/

   2. Black's Ruby for Rails (Manning). Read this not long after AWDwR. It provides much insight into the Ruby behind the Rails.

   3 (tie). Either Orsini's Rails Cookbook (O'Reilly) (the testing chapter is particularly useful if it's new to you)

   3 (tie). Fowler's Rails Recipes (Pragmatic Programmers). Both books are very good. If anything, 'Recipes' gets you movign faster, but you'll probably learn more from the Cookbook.

   opt. Ajax on Rails by Raymond (O'Reilly). An in Depth Reference to Prototype, Scriptaculus and rjs. Useful since there is no really good reference on these for the noob.

   opt. The Ruby Way by Fulton (Addison Wesley) An 'inside out' Ruby reference. Instead of going through classes and methods on by one, this book is organized by things one can do, with the classes and methods introduced in context. Not so much every day useful- but if you don't have access to a real liver rubyist, it's a good way to see how one might approach a problem.

   opt. The Pickaxe 2nd ed (dead tree format). Some folks just like to step away from the computer, and still think about computers.

   Other than books: The google groups for rails: rubyonrails-talk (general discussion. A great list btw good questions get answered very well usually. No attitude at all.)

   rubyonrails-core (the core contributors and rails internals)

   rubyonrails-spinoffs (mostly the ajaxy stuff)

   rubyonrails-security (created after an incident last year to spread urgent messages about rails vunerabilities, announcements only)

   The api docs:

   either at api.rubyonrails.org (rails)

   or caboo.se (another rails doc project)

   www.ruby-doc.org/core (Ruby core)

   www.ruby-doc.org/stdlib (Ruby standard library)

   Hope this helps,

   J.

   Show morethread
4. SteveCMay 2007
   I used three books in this order

   Agile web development with Rails (for learning rails initially)

   Beginning Ruby by Peter Cooper (for learning ruby)

   Rails Recipes (for doing useful stuff)

   While reading these I also worked on converting an existing web app into rails.

   Show morethread
5. bbasedDec 2011
   $2 dollars more expensive, 200+ pages and 50+ recipes lighter than my last Pragmatic Programmer ebook purchase of this type; Rails Recipes.

   Also, a few of those recipes I wouldn't consider "after the tutorial" material judging off chapter title alone. Like namespacing and view templates which are covered and covered again across material from the likes of the PeepCode or BackboneScreencast tutorials. But again, that's just judging from chapter titles I haven't read it.

   That said, it does seem very valuable but I think the price point is off compared to other books of that type, and other Backbone learning material.

   Show morethread
6. ngauthierDec 2011
   We included a few intro chapters so that people would be able to fully comprehend our examples. Think of them as pre-requisites.

   Keep in mind Rails Recipes was written by the incomparable Chad Fowler and probably had five figures worth of editing over a much longer period of time.

   Our focus from the start was to provide incredibly helpful and relevant code. If we had gone through pragprog the release would have been a few months later with less rough edges.

   xoxo ngauthier

   Show morethread