> If you want to delve deep into the core of Rails and present a coherent > picture of how it fits together, it'll likely have more currency in a year > or three than, say, if you conducted a broad survey of the best gems and > plugins around for particular tasks. Do you want this to be something you > write once and then set aside, or something you update alongside Rails for > the next however many years?
I'll second this idea -- David A. Black's "Ruby for Rails" is still a book I highly recommend for people getting started with Rails to really understand it -- and it was written in Ruby 1.x times. In fact, maybe an "updated' version of that book could give you a good model, since it goes right from starting with Ruby to understanding Rails internals (to some degree.) Cheers, Dave http://davidbolton.net On Tue, Apr 20, 2010 at 5:01 PM, David Lee <deathtoallfanat...@gmail.com> wrote: > Hi Ryan, > I think it might be worth thinking about (if you haven't) what kind of > lifecycle / niche the book is intended to have, because I suspect that's a > good way to make decisions about which things to include or expand on, and > which to ignore - especially in the ruby world, where things move so > quickly. > If you want to delve deep into the core of Rails and present a coherent > picture of how it fits together, it'll likely have more currency in a year > or three than, say, if you conducted a broad survey of the best gems and > plugins around for particular tasks. Do you want this to be something you > write once and then set aside, or something you update alongside Rails for > the next however many years? > On a related note, do you want to write a general (but hopefully definitive) > guide to Rails, which pays equal attention to people of all skill levels and > tries to cover every major topic (in moderate detail), or do you want to > write something targeted at say seasoned developers, or front-end guys, or > focusing on security, the enterprise, or whatever - which goes into unique > depth at the expense of breadth? > Not necessarily asking for answers (as you obviously have something up your > sleeve), I just thought the questions themselves might give you (or others) > some ideas. > cheers, > David Lee > > On Tue, Apr 20, 2010 at 4:43 PM, Ryan Bigg <radarliste...@gmail.com> wrote: >> >> Greetings, >> So I decided to take on writing a book and I'm looking for feedback. I >> know a lot of you are more at the advanced end of the scale so I thought >> this would be a great place to find out what to put at that part of the >> book. Here's my post asking about >> it: http://ryanbigg.com/2010/04/rails-3-book/. Any and all feedback is >> appreciated. >> For those of you who I've told things I probably shouldn't have told: sshh >> for now please :) Do not name names. Soon, I will tell all. >> -- >> Ryan Bigg / Radar >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to rails-ocea...@googlegroups.com. >> To unsubscribe from this group, send email to >> rails-oceania+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to rails-ocea...@googlegroups.com. > To unsubscribe from this group, send email to > rails-oceania+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-ocea...@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
