The maze book for programmers!

Algorithms, circle mazes, hex grids, masking, weaving, braiding, 3D and 4D grids, spheres, and more!

DRM-Free Ebook

The Buckblog

assorted ramblings by Jamis Buck

The Rails Way

31 October 2006 — 1-minute read

Michael Koziarski and I have recently written a few articles dealing with best practices in Rails. After we finished high-fiving and congratulating each other on having the same brilliant idea, Michael suggested that someone ought to consider a series of articles for Rails in a similar vein to the Pimp My Code Cocoa articles by Wil Shipley.

“Someone.” Hmmm…

To make a short story even shorter, we accepted the challenge, and The Rails Way was born.

Here’s the plan. You guys have code. We have opinions on how that code should be written. If you would like to submit your code to us, we will happily dig in and blog about how we would write that code. You can send your code anonymously if you’d prefer, but make sure you use a real email address in case we have follow up questions.

If you submit a full project to us, we will almost certainly not review the entire project. Instead, we’ll rifle through it and find some small portion of the project to focus on. For particularly…ummm…special projects, we might even write several articles, but in general you’ll only get one.

We’d prefer Rails code, but if you’re a real glutton for punishment, feel free to send us code in other languages and we might write about how that code would be better if it were written in Rails.

So, the word’s out. Any takers? Send all submissions to [email protected]. Read the official announcement at The Rails Way.

Reader Comments

Heads up: third link in has a typo.

Oops, thanks for the tip. Fixed.

Okay, this is very interesting. I have pet project I’d like to submit. I’m currently rewriting the project to support more features etc and it be great if I could get some feedback on certain parts. It’s not open source though, so how would we deal with that?


Sorry should have just checked the link. So once you’ve received the code you’ll assume you can publish it, okay that’s fair enough of course. I’ll try and extract a few bits that could be reworked and send them in, rather than dumping the whole application.

Great idea!

Excellent stuff guys!

“we might write about how that code would be better if it were written in Rails.”

Shouldn’t that read as: “how that code might be better if it were written in Rails?”

Otherwise either you believe that everything can always be done better using Rails technology or you are presuming that whoever will be submitting the code would be a lousy programmer.

tabrez, no, I meant it exactly as I wrote it. It’s called “propoganda.” :)