Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Introducing RMM, the Rails Maturity Model
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
tmornini@engineyard.com  
View profile  
 More options Feb 14, 4:42 am
From: "tmorn...@engineyard.com" <tmorn...@gmail.com>
Date: Sat, 14 Feb 2009 01:42:00 -0800 (PST)
Subject: Re: Introducing RMM, the Rails Maturity Model
I wanted to follow up on my post for clarification. I've seem some
incredibly
vehement comments flashing about the net regarding this thread, it's
clearly
struck a nerve!

It's clear that much of the Rails developer community isn't on board
with this
concept. I hear that loud and clear, and I understand the concerns.
Please
don't make me out to be some fiend for agreeing that there may be room
for
this sort of thing. :-)

I apologize to anyone who thought I was supporting something exclusive
and Java or Microsoft like. And, I apologize to Obie for even needing
to
say that, because I don't believe for a moment that he was suggesting
something exclusive and Java or Microsoft like in the first place. :-(

My largest interest was about growing the developer community to bring
in more developers to increase capacity in the Rails ecosystem itself,
and I think that's 100% clear in my supportive response to Obie's
idea.

Our customers at Engine Yard are screaming for more developer
capacity,
and in fact, TWO previous customers abandoned Rails (one for PHP and
the other for Java) simply because they could not find enough skilled
and
savvy Rails developers to move their projects forward.

What I was supporting was, perhaps, more education than certification:
a
commonly agreed upon set of practices could because a curriculum for
the large influx of new Rails Developers to follow so that us old
timers
in the space don't have to read code with multi-hundred line
controllers, for
instance. :-)

--
-- Tom Mornini
-- Founder and CTO
-- Engine Yard, Inc.

On Feb 12, 10:45 pm, "tmorn...@engineyard.com" <tmorn...@gmail.com>
wrote:

> We've been discussing this sort of thing internally for a few months.

> I strongly believe that Rails is being held back by a shortage of
> skilled developers.

> One of the most common questions our sales people hear is "Do you know
> any good developers?" :-)

> One small nitpick: I don't think it's fair to exclude the skilled
> single developers out of the highest level certification because they
> cannot pair program. I think pairing works, but good code is good code
> at the end of the day. A strong organization with multiple developers
> working on a project is a benefit, to be sure, but I don't see it as
> part of a skills/deeds based certification.

> I'd say the same thing about Positive customer testimonials. After
> all, a dev shop with a solid balance sheet is a benefit to many
> customers, but are we going to require open books before
> certification? :-)

> --
> -- Tom Mornini
> -- Founder and CTO
> -- Engine Yard, Inc.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google