Home > Community > The Joel Test – How do you fare?

The Joel Test – How do you fare?

Have you ever heard of The Joel Test? If not, go read it now.

Have you read it yet? No? Go on, read it!

Okay, welcome back!

What I’m curious about here is how well the U2 (even the wider MV) community fairs along these lines. Support for source control is a bit behind and from talking with people in some other U2 shops, the pervasion of real modern tools isn’t too crash hot. I’d be really surprised if any of us get greater than 9 but equally surprised if we were below 4 for anyone with more than 4 developers.

So let’s hear it. Give your honest answer (don’t sugar coat it!).

Although your answer will be anonymous (feel free to elaborate your scores in a comment however!), I’ll kick it off by giving the results as I see it for where I am now.

We scored 5 out of 12. Not completely horrible, but not ideal either. I’ll post the blow-by-blow break down in the comment section for those that are interested.

So, how does your establishment fare?

Categories: Community Tags:
  1. February 21, 2010 at 9:52 am

    1. No, not for our U2 system. We have backups of each version of code that goes in, but backup copies are not source control. (0/1)

    2. No. Getting a release in an environment is more like trying to plan a successful invasion of a medium island nation surrounded by 100 metre tall cliffs with only spoons, rubberbands and Elvis impersonators at your disposal. (0/2)

    3. No. We do make daily (hourly?) cups of coffee however. Apparently that doesn’t count either. (0/3)

    4. No. I wish. We have a incident / service request / time recording system, but it fails miserably at even been close to bug tracking software. (0/4)

    5. Yes. Finally! Touch down! Although not strictly 100% of the time, we have a big push in code quality and try to fix know bugs in any code we touch unless it is impractical. (1/5)

    6. Yes. Our managers have actually been on top of keeping up to date schedules of current and future changes / fixes / projects. Not to say the business doesn’t have them ‘changed’ occasionally, but that’s just the nature of the beast. (2/6)

    7. Yes. At least most of the time. It really does solve arguments later down the track and is a great reference piece. (3/7)

    8. No, but we have fun. Occasionally I do long for a quiet office with a door though. Maybe a window view… of the beach… in Barbados. (4/8)

    9. No. As attractive as ‘green screens’ are, I don’t think they count. We’re trialling the BDT at the moment, but so far it has been a flop for our situation. Some of us use wIntegrate Editor, but when you compare it with the tools for MySQL and C#, well, sometimes I can’t wait to get home to program on my own computers… (4/9)

    10. No. Suprisingly, this is something that we had, but no longer do. We had a QA team when I started, but all have since retired, not to be replaced. (4/10)

    11. Yes. I wrote code during my interview. Not that I have ever seen UniBasic (well, I did download the manual a few days earlier) before here. (5/11)

    12. No. It happens sometimes, but not nearly often enough to say it is systematic. (5/12)

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: