While we're talking about books, I picked up a copy of "Design Patterns in Ruby" by Russ Olsen[1] when it came out a few months ago. I don't own, nor have I read the "Gang of Four" design patterns book. This book provides enough background on several standard problems, and how they are typically handled in Ruby. For each case, he also discusses pattern abuse and provides pointers to existing Ruby code/ projects that implement the techniques. Rails is mentioned many times. It is a small book and is clearly written. It is _not_ a language reference. However, it does provide a good introduction for how to think about problems in Ruby.
[1]: http://www.amazon.com/Design-Patterns-Ruby-Addison-Wesley-Professional/dp/0321490452/ On May 5, 8:44 am, Deb Lewis <[EMAIL PROTECTED]> wrote: > On Sun, 4 May 2008 20:54:08 -0700 (PDT), [EMAIL PROTECTED] wrote: > > I've started learning Ruby/Rails last year... > > I'm currently going through Ruby for Rails (I've read AWDWR already). > > Good choice with "Ruby for Rails" - I think it's a very effective book > for learning Ruby and is the one I recommend to newcomers. Introducing > material from the perspective of developing for rails provides a focus > and realistic examples, and some of the explanations of language > features are the best I've seen from several different Ruby books. > > And another book tip: I recently picked up a copy of "The Ruby > Programming Language" (David Flanagan and Matz) and as I'd hoped it > fills the void in my Ruby bookshelf for a concise language reference. > This is a good book for people who want a straight reference rather > than an intro-level tutorial or the kind of snippets you get in > cookbook-style books. > > ~ Deb --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
