10 Reasons Rails Does Pluralization

In the interest of world peace, here follows 10 explanations to why Rails does pluralization. Pick the one that’ll make you the most calm:

  • A point of argument: Pluralization is really meant as a long-running practical joke instituted to cause a good flame-thread every once in a while. There’s nothing like the fresh smell of napalm in the morning and all communities need a cleansing now and then. It makes it possible for us to be so ultra-nice the rest of the time without going suicidal.
  • Gives a sense of accomplishment: Since the rest of Rails is so easy, we needed to put in at least one piece that would feel like an accomplishment when you finally learned the ins and outs of it.
  • Love it or leave it: Pluralization is a posterchild for the entire philosophy of Rails. If you can’t deal with it either by acceptance or by turning it off, it saves you a lot of trouble walking away today rather than three months down the road when you learn that Rails is soaked in opinions like this.
  • A rite of passage: Similar to the point of entry, but more profound. Once you accept the true wisdom of pluralization, you will have completed your cultural transformation and become a true Railer. I can count on you know to do any bidding and your path to rails-core as been made.
  • Them against us: In order for communities to yield, they need controversial arguments where they can clearly take side and talk about “the others”. It makes the group tighter and happier.
  • A tough problem: Since Rails is so bent on solving all the easy problems and with the least amount of energy, we needed a hard problem, like the English language, to tickle us as we work on the otherwise mundane details of creating a web-application framework.
  • The learning curve: Since David is not a native English speaker, he needed some way to practice those irregular inflections. What better way than to embed the challenge in every day software.
  • It’s the color of the bike-shed: When you enter Rails, it can seem like an overwhelming experience that almost sucks you in. A good way to reaffirm your identity, and that you don’t just accept anything, is to complain about the color of the bikeshed. You now did your part of scepticism and can partake in the lovefest without feeling like a fanboy.
  • Beautiful code leads to happy programmers: One of my prime inspirations for still doing programming is the possibility of creating beautiful code. I consider the singular/plural splits as employeed in Rails to constitute beauty. Removing it would make Rails appear less beautiful and that would make me sad.
  • David is insane: This is the summary category. If you found none of the others to fit, just ascribe pluralization to insanity. If you like the rest of Rails, you can even put the positive spin that “all genuises are a little crazy”, and if you don’t, you can use this point to prove that Rails really is evil.

Driver wants in on Ruby on Rails

Obie Fernandez retells a cute story from the VP of Marketing at ThoughtWorks, John Guerriere, who met an upcoming Rails developer as his driver to the airport:

john: i was going to the airport and the driver (the car service we use) asks if i know martin fowler.

john: i said yes, why do you ask…

john: he shows me his RoR Agile book by Dave Thomas

john: He taught himself RoR and loves it….

john: Smal world…He used to be a developer b4 he moved from london here…hard time getting a job…

Jobs, jobs, jobs: Hiring Ruby on Rails is hot

You take off for just a little vacation and come back to an inbox stuffed with job offers for Ruby on Rails:

  • LookSmart, based in San Francisco, is putting their enterprise app on Rails — a dynamic advertising marketplace managing millions of listings and bids, syndication partners, integration with CRM, credit card processing, web services APIs, etc. They’re working with Mike Clark and James Duncan Davidson to help bootstrap this project, and they’re looking for a top-notch, high-energy lead for the team, plus an additional engineer. A great opportunity to get paid to work in Rails on an app that’s central to a public company’s mission. If you’ve got the chops for either role, they’d like to talk to you. Contact Bert Knorr (bknorr_at_looksmart.net) for more info.
  • Naviance is looking for a designer with Rails experience. Especially Ajax and Ajax on Rails experience. The person will be working with Chad Fowler, who just joined the company as their lead developer.
  • Digital Age Media is looking for an experienced Ruby on Rails programmer to work on an online game. The work can be done remotely. Experience with video game theory and programming is a plus, but is not required. If interested please send an email with a resume, links to your work, rates, and availability to jobs at digitalagemedia dot net.
  • Free The Slaves is looking for a volunteer (unpaid) Rails developer to create an e-commerce system for the organization.

A List Apart 4.0 uses Ruby on Rails

A List Apart is an institution in web design. I’ve learned more than a few tricks over the years from this venerable magazine and its therefore with great honor that I see the newly relaunched version 4.0 is a Ruby on Rails application. Congratulation to Dan Benjamin, Zeldman, Erin Kissane, and the rest of the team behind ALA.

Comparing WebObjects to Ruby on Rails

Deirdre recently gave a presentation at BarCamp that compares the implementation of the same application in Apple’s WebObjects to Ruby on Rails. It includes this graph that contrasts the code-base size of the WO application to the Rails version:

Convince your manager to let you use Ruby on Rails

Zed Shaw has compiled a long list of suggestions on how you can get your manager to let you use Ruby on Rails for your next project. It’s full of goodies including this strategy of dealing with the ill-informed ‘does it scale’:

For example, they say, “It needs to handle 500 connections/second.” Don’t let them say “users”, “users” means nothing. Then you go test their current WizBangOMatic and find it only handles 10 conn/second. You can then come to them and say that Rails can’t do 500 conn/second, but it can do better than the WizBangOMatic which only has 10 conn/second performance. It’s evil, but it puts the performance harpies at rest.