Actually beginning as a Rails programmer right now is a little bit wooly: the documentation is pretty spread out, so you basically need strong google-fu or a mentor. It looks like the 3rd edition of Agile Web Development with Rails comes out in October (http://www.pragprog.com/titles/rails3/agile-web-development-with-rails-third-edition) which will almost certainly make it a lot easier.
For now, the best bet seems to be to read through most of the second edition of Agile Web Dev. so that you understand some Rails theory and practices. (basically, parts I and III) Then, follow along with one or more Rails 2.0 tutorials: I used Akita's to make the transition from 1.x to 2.x after about 6 months of inactivity. (http://www.akitaonrails.com/2007/12/12/rolling-with-rails-2-0-the-first-full-tutorial) Your mileage may vary, so feel free to consult other tutorials.
After that, the docs/api at rubyonrails.org are probably going to be your best friend, particularly in conjunction with Agile Web Dev.
Tips for newbies:
You really, really want to be using Ubuntu to develop Rails apps. The initial setup can occasionally be a bit of a headache but a quick expedition to google with any errors you're having will almost certainly result in the solution. The Ubuntu community is amazingly good and there are some pieces of software that will hit there significantly before they will on OS X, the other candidate for serious Rails dev. Using Windows for Rails dev seems to be filled with naught but pain.
A lot of people in the Rails community are yammering about how great Postgres is. It's probably not for you, unless you've used it before. MySQL is much more batteries-included and will probably be more than adequate for any app you're writing early. Database issues are just things you shouldn't have to worry about yet.
Heroku is a pretty good early hosting solution, unless you already have a Rails-compatible host. I don't like using them as a development platform, but that's largely personal taste and a toleration for sysadmin-y things.
Learn Ruby. No, not Ruby for Rails. Learn Ruby. Other than drive/intelligence the single biggest commonality I've observed among great Rails developers is that they know how to use Ruby well. Thinking as a functional programmer is tremendously helpful, so at least look at functional languages (I recommend Scheme) and practice programming Ruby with a functional style. Higher Order Perl is a pretty useful exercise book, even though it's not explicitly intended for Ruby. It will make your code better. Or at least suck less.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment