Wanted: top-notch developers only, or not

Donnie recently posted this which made some noise. Before we go any further I’d like to say that I liked it a lot and found it very interesting although I’m going to sound very critical about it. Exploring this kind of ideas will benefit us, whether we use them in the end or not. At least if we don’t we’ll know why we believe they’re not appropriate to our own little world.

I’ll have to split my comments in a few different posts because I was told the previous one was too long. Sigh. Let’s all thank television and its commercial breaks for unlearning our kids to focus more than a few minutes at a time.

Keeping in mind the Pareto principle (20% of the effort produces 80% of the results), I’ve come up with some ideas. The core of these ideas is creating a development community composed only of top-notch contributors […].

Here I’d like to warn the reader who’s not used to corporate bullshit (tell your mommy that in this context it’s not a bad word but a technical term). Donnie uses the Pareto principle in the good way: as a clue to what the problem could be or as a lead to an idea. However, general principles like this one were made up by bright minds and are abused by corporate robots everyday. It’s so easy to derive, from such theories with a certain amount of undeniable truth, a pretty looking analysis that doesn’t fly or a practical application that smells funny. It’s so comfortable to hide behind numbers and tell upstream (the boss) “Hey it’s not me, it’s the numbers”. When you use such tools blindly and push them too far you may end up crashing into a wall. And the wall in Donnie’s case was top-notch.

It’s true that we some of us I tend to procrastinate a lot and then do the real work in short bursts. It’s also true that my neighbors’ house popped up from the ground in a few days and that months after they’re still working on who-knows-what inside. And it’s also true that there’s a small group only of Gentoo developers who seems to be doing most of the work. Now, do we know how much procrastination participates to creativity? Don’t you know how long it takes to do the wiring, plumbing, painting etc… compared to just building the walls? And do we even have a vague idea of how much so called slackers contribute to the Gentoo ecosystem?

I don’t have exact numbers but it seems to me that the 20% of top-notch developers are a fluctuating population constantly drawn from the 80% tank of slackers. And that if we got rid of the 80% we’d have trouble maintaining the number of top-notch developers. And that’s just the tip of the iceberg. Top-notch developers won’t do chores. Or not for long. Top-notch developers often can’t be bothered to answer users. Top-notch developers don’t always behave well so it’s a good idea to dilute them. Top-notch developers may not want to handle obscure package herds. Oh, and do top-notch developers write a lot of documentation? I could go on like this forever.

By the way, I’m not meaning we should keep the bad apples. Some of you may know which side I’m usually on when devrel needs to vote on retiring annoying developers. For those who don’t, let’s just say I don’t have a high tolerance for counter-productive behaviors. But between bad apples and top-notch developers there’s a lot of room that I find very comfortable.

Here’s another provoking thought. One could argue that if the 20% were that top-notch, they would naturally fight their way up to 30%, 40%, etc… If this population is so fit for its environment and purpose then it surely has this very basic evolutionary skill. If not then they’re not top-notch in my book.

So you think you’re a top-notch developer? Try and make me become one and we’ll know for sure.

5 thoughts on “Wanted: top-notch developers only, or not”

  1. I’m not a top-notch anything. I’m an arch tester, I watch stuff compile (and occasinally break). And contrary to what some believe, this is mostly chore-work (including, but not limited to, kicking upstream’s rear end).

    Your observation of the 20-recycling-the-80 mechanism I found very insightful. And I hope Donnie is aware of it.

    As others have noted, Gentoo quite probably is never the top priority for anyone, even if you discount family, friends etc. If I had to choose between my job and Gentoo, it’d be my job, no two doubts. And that is the point: the mechanisms Donnie describes are fit (to an extent) for people who have contracts. Thos contracts usually are about livelihood of the workforce, so the motivation to please the other party is much higher than with volunteer work.

    I’m with you that the bad apples need to go before they poison the whole barrel. But what do you do with the dev who does nothing for a month then produces a stunt that leaves you weak in the knees for its sheer brilliance? What about the not so clear cases?

  2. It seems like the crux of our disagreement is the definition of a top-notch developer. Guess I know what my next post on this broader topic will be …

  3. I write documentation!

    So yes, some of us do. For some of us, it’s almost all we do. 🙂

    But yeah, over the last few months, I’ve noticed that I’ve started a pattern of slow, minimal work followed by sharp bursts of frantic activity. It’s taken 4 years of contributing to get to this stage, though. I wonder how long it takes for other developers?

  4. Reminds me of this exchange attributed to Stalin:

    “How many films do we make yearly?”
    “150.”
    “How many of those are good?”
    “Two.”
    “Then make only those two from now on.”

  5. Donnie,

    Although it looks like I disagree with you I was only debating. Part 2 of my comments to your posts is much less critical and reconciliation is planned for part 3. Stay tuned.

    Denis.

Comments are closed.