3 ms·
15 hours of Ruby tutorials? I hate to be a killjoy, but I recall there being a screencast that showed you (with, granted, a whole lot of magic pixie dust) how t
by swombat 16y ago
15 hours of Ruby tutorials? I hate to be a killjoy, but I recall there being a screencast that showed you (with, granted, a whole lot of magic pixie dust) how to build a blog in 15 minutes.
I'm not entirely sure that "More is good" in this context. But then, I know Rails already so I'm not part of your target market, I suppose.
Still, I would feel somewhat daunted by 15 hours of tutorials and 1000 pages of documentation. Sounds more like .NET than Rails.
- ryanhuff 16y agoThere is a place for detailed coverage of the different topics. The 15 minute blog tutorial is great to give you a taste, but when you are new to a platform, its nice to have a more comprehensive resource that steps you through the details.
- mhartl 16y agoYou really need to watch "Lesson 2: A demo app". :-) It's my version of the "15-minute" blog, and even it is a lot more than 15 minutes because I go into considerably more detail. In the process, I enumerate all of the toy demo app's many failings, and then fill in the gaps in the subsequent 10 lessons. (If you don't want to buy the screencasts, taking a look at the free online book at http://railstutorial.org/book http://railstutorial.org/book will give you a sense of what gets covered.) The bottom line is that there's a world of difference between a tiny toy app and a real-world production app. The Rails Tutorial screencasts do teach you a toy app along the way (Lesson 2), but preparing you to make industrial-strength webapps is their raison d'être (Lessons 3–12). As it turns out, that takes more than 15 minutes. :-) P.S. The "1000 pages" number included the page count of the Rails 2.3 Tutorial book, which many people won't need (though it's still useful for people with legacy apps). The Rails 3 Tutorial book itself is only about 500 pages, and I've change the wording on the site to make it sound less intimidating. Thanks!
- deleted 16y ago[deleted]
- mshafrir 16y agoNote that this screencast offers a lot more than basic Rails. You get other concepts like basic Ruby, Git, and TDD.
- r00k 16y agoAmazing that people can complain that an open source tool is too well-documented. The famous 'build a blog in 15 minutes' was Rails' elevator pitch: intriguing, representative, but by no means a complete picture. You still needed a full reference to get real work done. That's what this is.
- swombat 16y agoThere's plenty of Rails documentation, as well as for-money books and screencasts, already in existence. Generally, the successful ones tend to be tight and light. "Agile development with Rails", not "Extensive 1000-page guide to Rails". Worth also pointing out that I'm criticising the commercial effort here, not the general goal ("help people use Rails"). Also, as I mentioned, I'm not part of the target market, so my criticism may be off-base.
- mhartl 16y agoYou're right that 1000 pages might be a little crazy. As I noted in another comment, that total included the pagecount of the Rails 2.3 Tutorial book, which comes for free with any PDF or bundle purchase. The Rails 3 Tutorial book itself is only around 500 pages. I've updated the descriptions on the Rails Tutorial website for clarity.
- kingkilr 16y ago1000 pages really isn't that much, Django's documentation is about 800 pages printed last I checked.
- Bitmobrich 16y agoIf you want to be a rails developer it is going to take more than 15 minutes.