Skip to main content

Books: Ruby for Rails

I just finished a series of blog posts called Ruby: A Python Programmer's Perspective. Now, I'd like to finish up by writing a quick review of Ruby for Rails. Overall, it wasn't bad. If you can't tell by my other posts, I learned a lot. I really enjoyed the middle of the book which covered Ruby, but I got bored toward the end when the author spent three chapters improving an ecommerce site.

The author appears to be an intelligent, native English speaker, however his grammar patterns made it difficult for me to read the book quickly. Here is an example:
We must be able to determine before executing an action what state we're in with regard to the visitor's login status and its importance. [p. 440]
Translation: "Don't show the login form if the user is already logged in."

Here's another example:
Facility with Ruby will stand you in good stead in your controller programming, as well as your model programming. [p. 438]
Translation: "If you don't know Ruby, you're going to have a hard time writing controllers and models." Note, this sentence is in chapter 16. I would argue that anyone who has made it to chapter 16 knows that you need to know Ruby to be proficient with Rails ;)

By and large, the code was pretty good. However, there were a few times when I was pulling my hair out. Here's an example:
def Work.all_periods
find(:all).map {|c| c.period }.flatten.uniq.sort
end
This ActiveRecord code pulls down every musical Work in the entire database in order to get a list of the 5 or so musical periods. I know that people love to say that Rails doesn't scale. Given this example, I'd have to agree. I would have preferred to see the code that makes the database do the hard work instead of downloading the entire table to the application server.

One thing I will say about this book is that a lot of people have read it. I like to submit errata to authors. If I find a technical error in a book, it's a good sign that I'm paying attention, so I try to find as many errors as possible. When I went to submit errata for this book, about half of the errors I found had already been submitted by other readers. That was pretty impressive.

In summary, if you need to learn Ruby in order to use Rails, this book is worth reading.

Comments

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;)

In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3, Erlang, and the original Lisp machine. The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts.

Now, I'm sure that many of these ideas have already been envisioned within Tunes.org, LLVM, Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway.

Rather than wax philosophical, let me just dump out some ideas:Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code." I bet it&…