If you're working professionally with RoR buy few commercial books on Ruby and Rails. The cost is negligible when you consider the savings in time that you will get when learn from a good Rails/Ruby book. Sure, Django has a free book on the basics of it and there is Dive into Python series but the number of books on Rails is much greater and they are professionally edited and are of better quality.
The lack of free books is an issue but you get what you pay for.
"You can buy a good book" is not a valid response to "Ruby's documentation sucks". I have all those books, and I don't feel compensated for Ruby's crappy documentation.
Comments
He brings up a good point w/ documentation. Ruby's has left me wanting in more than a few situations.
If you're working professionally with RoR buy few commercial books on Ruby and Rails. The cost is negligible when you consider the savings in time that you will get when learn from a good Rails/Ruby book. Sure, Django has a free book on the basics of it and there is Dive into Python series but the number of books on Rails is much greater and they are professionally edited and are of better quality.
The lack of free books is an issue but you get what you pay for.
"You can buy a good book" is not a valid response to "Ruby's documentation sucks". I have all those books, and I don't feel compensated for Ruby's crappy documentation.
There are many Ruby libraries that haven't been documented anywhere, online or offline. Random example: bitset.