Feature
Post

Category
General

Build Your Own RoR Web Applications

Sitepoint’s RoR book: Build Your Own RoR Web Applications

We’ve all seen it. Any time you visit Sitepoint, you’ve probably been hit with the ad for their Ruby on Rails book, titled “Build Your Own Ruby on Rails Web Applications”, by Patrick Lenz. Dubbed as “The Ultimate Beginners Guide to Ruby On Rails”, I figured the book was pretty good.

Still, I had no intent to learn RoR simply because I didn’t have time. Then came the opportunity for me to review the book for Sitepoint thanks to Reviewme, and I finally decided to take a look at the book and see what I could learn. For this review I’ll be using the first four chapters of the book, which are currently available as a free trial so you can get a taste of the book before you purchase. I’ll be breaking down the key points of each of the four chapters, with a final wrap-up at the end of the review.

Chapter 1: Introducing Ruby on Rails

The first chapter presents you with a lot of history on RoR. Since I knew so little prior to reading this, I learned a whole lot that I never understood about RoR. Rails was actually extracted from Basecamp, the lead project of 37Signals, and then released - something I would have never expected. The first chapter also touched on three principles that differentiate Rails from other development languages. They were:

  • Convention of Configuration
  • Don’t Repeat Yourself
  • Agile Development

Each category was than expanded with a description of what exactly each principle meant in everyday language for us non-programmers. Finally the first chapter wraps up with a summary of what you can expect to get out of building your own sample application by following the instructions throughout the book, which lets you create a cloned site of Digg.

Inside the pages - Sample 1

Chapter 2: Getting Started

The second chapter is all about getting your system setup and ready to develop your first RoR application. You install three key components, which the book outlines how to install depending on your Operating System. They are:

  • The Ruby language interpreter
  • The Ruby on Rails framework
  • The MySQL database server

The book does a really good and straightforward job at describing the setup process. Windows, Mac OS X, and Linux are all covered. Towards the end of the chapter you learn how to setup “one directory setup to rule them all”. Finally, you’ll start up WEBrick, a small web server written in Ruby. While it has almost no functionality, you have started up your first Ruby Application.

Inside the pages - Sample 2

Chapter 3: Introducing Ruby

Chapter 3 is a very informational chapter that outlines on what exactly Ruby is, and how a object orientated language works. It talks a lot about how Ruby objects communicate with each other, how to read and write Ruby code, standard output and core classes, running Ruby files, and control structures. You can learn a hell of a lot of information on Ruby just from this one chapter alone - it really does an excellent job going over all the different elements that make up the Ruby Language.

Inside the pages - Sample 3

Chapter 4: Rails Revealed

The final chapter in the downloadable sample of “Build Your Own Ruby on Rails Web Applications” covers the Rails in Ruby on Rails. In it Patrick Lenz talks about using three different environments when developing in Ruby: development, test, and production. Next you learn how to setup the database for Rails - quick, easy, and straightforward. There is then a nice description of the MVC (model-view-controller) architecture that Ruby uses. This includes describing the differences between models, controllers, and views.

The chapter also contains information on generating code with Rails, and testing and debugging with RoR.

Summary

The first four chapters were very helpful in giving me (a non-programmer) a much better understanding on Ruby. It’s easier to understand why it should be looked at as the programming language of the future, because it helps make things so much easier and can greatly improve development time.

Reading these first four chapters really sparked my interest in Ruby, and it’s something I’d really like to try to learn more in depth in the summer months. The book itself does, in my opinion, a wonderful job by organizing the information in each chapter really nicely, and incorporating a lot of visual graphics to give you a much clearer understanding of the instructions and how things work in Ruby on Rails.

If haven’t read the book, you’re thinking about giving RoR a shot, or you just want to learn a little more about the programming language that is helping aid the boom in web based applications, this book is for you. With 163 pages just in the first four chapters, you are definitely getting your moneys worth by purchasing the book, which contains over 400 pages and digs a lot deeper than the intro chapters, and will help you put together your first application.

You can grab the first four chapters for free from here, or purchase the book at Sitepoint.

Note: The preceding was a paid review.

  1. By Kabari posted on February 24, 2007 at 2:54 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Good post. For those interested in learning RoR, I suggest reading this book first, then going on to read Agile Web Developement with Rails from Pragmatic Programmers.

    The difference is that for Rails Noobs, the SitePoint book is much easier to go through the first think (imo). The Agile book gets pretty dense about 200 or so pages in, so it’s good to have all the examples from teh SitePoint book under your belt before you really get into the nitty gritty of ActionPack etc.

  2. By Jordan posted on February 24, 2007 at 7:15 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I’ve been considering books on RoR, and your lovely review is what’s going to make me get that Sitepoint book.. And apparently reviewme.com enjoys your article just as much ;)

  3. By Jordan posted on February 24, 2007 at 7:16 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    you’re!? *headdesk* your :’(

  4. By aj posted on February 24, 2007 at 8:02 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Don’t worry Jordan, it’s a lot better to make spelling mistakes in comments than Articles…readers tend to get annoyed with that :P lol

  5. By Gonzalez posted on February 26, 2007 at 4:39 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Just look at the trackback/pingback section. This is clearly a paid review.

  6. By aj posted on February 26, 2007 at 5:42 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Yes it is a paid review…what does that have to do with anything?

  7. By Jordan posted on February 26, 2007 at 6:25 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Gonzalez, did you even read the article? “Then came the opportunity for me to review the book for Sitepoint thanks to Reviewme…”

    Clearly he didn’t. Shame on him.

    Also, are you using gravatars or mybloglog thingies?

  8. By aj posted on February 26, 2007 at 6:34 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I’m using gravatars…not even sure if the plugin has ever worked. If you (supposed) to have a gravatar, let me know so I can get this fixed.

  9. By bob posted on February 26, 2007 at 6:41 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I just unsubbed from your RSS feed. If I wanted to read an ad at least tell me it is an ad….paid review?! You’ve got to be kidding.

  10. By aj posted on February 26, 2007 at 7:37 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    @bob - You’ve got to be kidding me. A true reader, you are not. This review is not an ad. All of our reviews are 100% unbiased, regardless of whether they are free or paid. Look around, because their are plenty of other resources (ie: Fadtastic), that accept paid reviews. If I thought the book was shit, I would say it. If i thought you were a real reader, I would say it.

    So there’s my answer.

  11. By adiaha posted on February 26, 2007 at 9:03 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Why are people upset that you got paid? Yikes, I am happy that you made money. Good for you and while I did not read the etire review, the first half was really good. I now know what ROR is and will consider learning.

  12. By aj posted on February 26, 2007 at 9:08 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Thanks adiaha

  13. By Kyle Korleski posted on March 2, 2007 at 9:45 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I am thinking about learning Ruby on Rails.

  14. By KOD posted on March 3, 2007 at 5:25 am
    Want an avatar? Get a gravatar! • You can link to this comment

    I just read your review, not out of interest in RoR, but because I’d like to explore the world of paid reviews. I have to laugh after reading some of these comments. What review writer (worth reading) DOESN’T get paid?! Whether it’s a print review, TV review, online review…come on folks, who do you seriously think is going to take the time to read something (even just the first four chapters–which you at least are honest abou from the opening), form an opinion, put it into words that the common reader can understand (keeping in mind that the “common” reader is at about a 3rd grade level), and then review and rewrite (as needed)…
    If a writer doesn’t think his/her time and effort has anyvalue, why would I think his/her opinion has any value?

    AJ, keep up the fine work!

  15. By Dan posted on March 6, 2007 at 5:39 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    With respect to the comments on paid reviews, there’s a big difference between an impartial party paying for a review and the company whose product you’re reviewing paying for it (which is the case here, although it wasn’t clearly stated as such). The former is a review, the latter is an advertisement (regardless of how “impartial.”) Do reviewers deserve to be paid for their work? Absolutely. But the true source of payment needs to be clearly identified. It wasn’t here.

  16. By anthony gippo posted on March 6, 2007 at 6:05 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Are you serious? Its not a real review, its an ad, the “review me” people even state this on their site :
    “Because our reviews are not formatted to look like ads, publishers are able to deliver more attention and value than through advertising via any other marketing channel.”
    check it out : http://www.reviewme.com/why.php

    So what happens if a “review me” reviewer does an article saying an product or service sucks? how much work do you see them getting in the future?

  17. By aj posted on March 6, 2007 at 6:27 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    If a product sucks, the company that purchased the review spot is supposed to get feedback on how they can improve, or face the hard truth about a product / service being poor.

  18. By aj posted on March 6, 2007 at 7:00 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    To further up my comments,

    @Dan - Sitepoint pays reviewme, who in turn than pays me, regardless of whether or not the review is favorable or unfavorable to the company / product / service / etc. Quoted from Reviewme’s F.A.Q’s:

    “We do not allow advertisers to require a positive review. The vast majority of reviews are measuredly positive, although many do contain constructive criticism. We view this as a bonus: how else can you quickly and cheaply get feedback on a product or service from influencers?”

    In a way, this makes Reviewme the “impartial party”, as we as publishers get paid regardless of what we say. Yes, the money may be put up by the company who wants their service reviewed and not by a complete outsider, but they do not control what the reviewer has to say about their product/service.

  19. By DBM posted on March 6, 2007 at 8:34 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    I write legitimate reviews for a magazine that pays me a nominal fee. I also write legitimate reviews for my own blog along with other articles that translate into ad revenue at times.

    Both are respectable ways to be paid for writing reviews.

    I would NEVER accept a payment from the company that owns the product for the express purpose of writing the review, however. That’s entirely unethical, no matter how you slice it.

    At the very least, the article above should disclose the fact that the manufacturer was PAYING FOR IT TO BE WRITTEN. When an ad looks too much like an actual article in a magazine, for example, most respectable magazines will add the words “paid advertisement” or something to that effect. This article did not.

    (Granted, the article above did state that the opportunity to review the product came via Reviewme, but the ordinary reader has no idea what that means.)

  20. By aj posted on March 6, 2007 at 9:16 pm
    Want an avatar? Get a gravatar! • You can link to this comment

    Comments now closed, discussion is getting way off topic. Count on this being a Friday Focus topic discussion for sure.

  21. TrackbackWhat does a ReviewMe review look like? | ReviewMe Blog» Savaitgalio skaitiniai #16 Archyvas » Pixel.lt金星,你好! » Blog Archive » Ebay的推介AuctionAdsReviewMe | Zarabianie na pisaniu bloga | Zyski online - zarabianie w internecieDevlounge | Sitepoint’s Ruby Book for FreeBloggerOfTheWeb “More Than Just A Blog” » Blog Archive » Blogging Tips: Let Advertisers Offer You Reviews.