Customer Reviews

Ruby on Rails For Dummies

5 star:		(3)
4 star:		(5)
3 star:		(3)
2 star:		(1)
1 star:		(3)

 

 

First I want to make clear who this book is for an who it isn't. If you are a real programmer, not someone like me with just a smattering of PHP and JavaScript, you will find this book entirely too basic. It is a true Dummies book, an introduction not a complete course. If you tried the Ruby on Rails (RoR) bible, Agile Web Development with Rails, and found it a bit over your head, you should find this an kinder and gentler primer.

Ruby on Rails for Dummies assumes absolutely no prior programming experience. It doesn't even assume any command line knowledge. It does assume a decent grounding in HTML and CSS, but that's true of any web based programming book. Going directly from a visual web layout tool to RoR will be too big a leap. It would be like trying to complete a 10 K run after practicing by jogging a mile three times a week for a month or so. You might get through it but the process would be more than a bit painful. But if you have your hand coding chops but no real programming background you should find this book a gentle introduction to Ruby on Rails.

It made a number of ideas clear that the Agile book assumed I was already familiar with. It provides a nice quick start to RadRails, a free RoR development environment, which somewhat insulates you from the straight command line approach taken my more advanced RoR texts and provides a pre-packaged Ruby on Rails development environment. There is also a short introduction to the Ruby programming language. It's very basic but probably helpful.

Ruby on Rails for Dummies proceeds step-by-step through a couple of very simple RoR applications. It's enough to get your feet wet and make more advanced books approachable. It does not provide enough of a knowledge base to actually go out and start developing web applications. You'll still need to get a more advanced book but at least you will have a decent foundation on which to build.

I could not recommend RoR for Dummies more. It is an excellent book to a person who is looking for what I was looking for: a cohesive intro into RoR.

I am not a programmer and I need to learn how to develop online application, i.e. database driven website (rather than static one using HTML and CSS alone) for our business.

After thorough looking around I decided to go ahead and jump on Ruby, and ride the Rails (the framework within which online applications using Ruby language are built).

The package is playfully called Ruby on Rails, shortly RoR (the book also explains how this name originated).

I chose RoR over other available tools out there like PHP, C# in MS Visual Studio or Java with Struts, and others for the sheer beauty of Ruby. [...]

RoR for Dummies is a bit more than an intro into RoR. It is a succinct primer for the Ruby programming language itself, Rails framework, HTML(!) and RadRails. RadRails is one of the available RoR's IDEs - Integrated Development Environment. IDE refers to a software that integrates working with all the essential parts of RoR in one place (namely Ruby, Rails, HTML, CSS, and some database (MySQL is the 'native' database in RoR). Very much like 'word processor' refers to a software for writing and formatting text documents.

There are also a few paragraphs on databases spread around the book which I found very useful and informative. The book does not delve into CSS, which is understandable; CSS - albeit syntactically very simple - is a powerful formatting tool that can swiftly become challenging animal to tame if one leaves arena of coloring fonts and backgrounds. CSS is a subject matter of plethora of books.

All of the parts necessary for work in RoR are available free of charge for immediate download and use. For a novice, this may seem a daunting task but RoR for Dummies guides reader through the download and installation of all of the parts safely and painlessly. I had no problem installing any of them following the instructions in the book (running Windows XP).

The book is written in such a way that if one knows nothing about any of the topics (I think so, I cannot say about myself that I know nothing about these things), one can still proceed chapter by chapter and get all things done. There were only a handful of points in the book where I felt it was necessary to look elsewhere for additional explanations. And that was simply because I am a curious person and want to know the why's.

The book is also quite funny at times.

Of course that I have a slew of other books to go through in order to get efficient in using RoR. But again, I feel, that RoR for Dummies did excellent job in introducing me to the entire fleet of technologies involved in building an online application using Ruby, Rails, and HTML (the three covered topics).

On the margin, I have a good working knowledge of HTML and CSS. I have some knowledge of Ruby, as I am learning Ruby on my own (I have taken courses on Visual Basic and PHP to get my feet wet in terms of programming). I am also currently taking courses on databases - database design and SQL. All of these pieces are needed for building online applications.

One more thing, RoR/RadRails is not a Dreamweaver - although a huge amount of scripts is generated by Rails (hence the tremendous boost in efficiency of work), RoR/RadRails is not about dialog windows simplifying your job, it is about coding into what was prefabricated for you by Rails.

Barry Burd, Ruby on Rails for Dummies (Wiley, 2007)

You gotta love an author whose domain name is burdbrain. That said, Ruby on Rails for Dummies has exactly the same strengths and weaknesses as the rest of the Rails books I've read over the past few months. The biggest weakness, of course, is that the book is dated, like the vast majority of Rails books. Nothing to be done about it; software moves on, books are static. On the other hand, like the rest of the books, it's a solid tutorial in how to get yourself up and running on (an earlier version of) Rails. The datedness is not normally a huge thing, but since the database access methods have changed between then and now, those coming into this without some supplementary materials may find themselves confused when a number of examples error out. Still, as long as you recognize this and supplement with more recent online tutorials, this is a solid book. ***

The book goes all over the place. The author pulls out objects and methods out of thin air, doesn't explain how, where those objects are. And his attempt at humour is very lame. The book is incoherent, and at the end of the book, you really haven't learned anything. Leave this P.O.S. on the shelf. Look for a better book.

The book is good. Well written, and goes over the core functionality that should help you get up and running.

BUT for those that are just trying to get up and running, this book isn't for you.

Wait for another version to come out that is up to date. I spent 3 days just getting ruby to run on my machine. After I did manage to make some progress, I found myself stumbling over instructions that detailed the old version of RadRails that Barry was referring to.

If you can get past that - then yes - go for it! Otherwise, wait for an updated version.

I needed a jumpstart to learing more about Ruby on Rails and this book was the answer. Although most of the software listed is outdated, I easily converted the instructions to apply to the new software. It was a great tool and assisted me in my search for a better web design tool.

so this was my 1st experience and it's a little disheartening to find out this is for an old version of rails on a xp platform. It's well written, exciting helpful and engaging but I'd love to see a updated version of this. Barry does offer updates on the site but for 30 bucks and a lot of room for a new edition to the series I am still on the lookout or an updated version or a sequel. He holds your hand and provides plenty of cross reference from one chapter to another but be warned this is old and a lot has changed in rails. I commend him for the gui rad rails tool and the express setup. This will get you ready for the next book. Check out Chris Pine's pages and the pragmatic programmer site. I thank Mr. Burd for his book none the less.

This book is almost two years old which means it's sorely behind in the advances of Ruby. Worse, it depends on RadRails, an open source program that's constantly evolving. Mr. Burd's RadRails examples are completely outdated. For example, RadRails uses a new layout and uses new extensions on its files.

Worst of all, in spite of the author's flippant remarks that a Mac users should be able to follow along with the examples, his statement is simply not true. There are too many differences between Windows and the Mac OS. I wasted too much time following his directions believing his assessment of the Mac OS was correct. Fortunately I found plenty of tutorials online to skip his set-up instructions so I could get to the meat of his tutorials.

Finally, this is where he falls flat. He gives the reader just enough direction to create his little examples, but not enough solid explanation as to why these steps are taken and what code they create. He continually uses sloppy terminology (and unnecessary jokes) when explaining the intricacies of the code.

Skip this book and its careless job of being dumbed down. Find a tutorial online that fits your unique set up.

Good luck!

I work in the IT world, but knew nothing about RoR and just wanted enough of an overview to build a simple application that I had conceived. The book fit my needs perfectly.

My one gripe was that the book referenced several links for Mac-related tutorials and tools at the books website, but they did not exist.

That said, my disappointment was more than compensated for when I emailed the author, Barry Burd, and he quickly responded with several helpful tips. I later found several great blogs and other web resources for getting RoR running on the Mac.

This is a good introduction to Rails. It's the only beginners book that I've found that uses RadRails. The examples are all practical and there were very few typos/corrections. A few of the examples in the later chapters required much more explanation than was given in the book. I suppose the point of these advanced examples is to just introduce the reader to some of the more powerful and advanced features of Rails, but a pointer as to where more detail could be obtained would be useful. Good use of humour (even though much of it is lame) kept the book moving and enjoyable.