OK, I'm coming to rails late. I've played with Ruby on and off for about a year. I though it was a bit of a "kitchen sink" language until I got a good kick in the head by Neil Ford.
So this week I picked up this book (version 2) and I started reading it. It is, as far as technical books go, a page turner.
It gives a basic overview and the walks through an example as a tutorial.
I recommend you learn a little Ruby first (not necessary but makes working through the examples more focused on Rails rather than Ruby and Rails).
If you want to learn about Ruby on Rails and get an idea of what web development should be, read this book. THEN, the next time you need to start working on a site for a customer, sit down with them and start developing the site in real-time.
If they don't like Ruby, call it an "executable requirements description". Eventually, they might even think that the solution is good as is. If not, you still have a better explanation of where to go.
After Rails, I'm going back to RSpec and story tests and examine the maturity of developing a Ruby solution using TDD. I'm pretty sure it's already being done, so I just need to get on that learning curve.
This is a GREAT book. Get it, read it, TYPE in the examples - ok maybe download the CSS's and the style-sheet.
WARNING: the material related to OS X installation is a bit out of date. Use macports and install mysql, rb-mysql, rails, ruby (and I'm probably forgetting something), change your path to point to where that stuff got installed (probably /opt/local/bin/) and you'll be good to go - once you get mysql setup. There are some chicken scratchings here: http://schuchert.wikispaces.com/Ruby.RailsConfiguration.OSX, or do a google search. It'll be October 2008 before I actually put up good details, but it'll happen.
less
0 comments
Post a comment