Quoting Joel Spolsky, the Joel Test is a highly irresponsible, sloppy test to rate the quality of a software team. What follows are our results, 1.5 months after the birth of the new company.
In the light of maintenance programming, I'd like to add another question to the test: do you have coding conventions?. More on this later...
-
Do you use source control?
Yes, from day 1. We use CVS because we were used to it and because is well-known, so getting help is easy. -
Can you make a build in one step?
Yes. As a matter of fact, I like to script repetitive tasks as much as possible (three strikes and you automate) -
Do you make daily builds?
No, not yet. We have yet to integrate an automated build system into our practices, and we are procrastinating because currently we build our projects several times a day. Suggestions for automated build systems for Java server-side applications are welcome. -
Do you have a bug database?
Yes. We're evaluating JIRA and, if it was for me, we'd have bought it 15 minutes after installing. -
Do you fix bugs before writing new code?
Yes. Although I can't claim decades of experience, I've already lost count of the times I was given maintenance of broken code years after... If we fix our bugs as soon as possible, some maintenance programmers in the future won't be angry, for a change. -
Do you have an up-to-date schedule?
Yes, although currently we aren't at 100% of our project allocation, so sticking to a schedule is relatively easy. -
Do you have a spec?
Yes. Absolutely. A project without a spec is doomed. Been there, done that. -
Do programmers have quiet working conditions?
Yes (at least I suppose so...). This was one of the major gripes I had towards my previous employer, but now we're in an XIX century factory a dozen kilometers outside Treviso with designer studios, architects... We hear birds chirping when we open the windows, but I'd still like to ban all telephones. -
Do you use the best tools money can buy?
Yes. While there's still something to be bought, we definitely haven't skimped on hardware and software. -
Do you have testers?
No. As the company grows, we'll need them. Though Joel's arguments are sound, with our size it would be very difficult to have dedicated testers on team. -
Do new candidates write code during their interview?
No. In fairness, I have to say that, out of 6, 5 people had already worked together for quite a bit of time before joining this company. But this make a lot of sense... I think I was asked to write code only once in my latest 20 interviews. -
Do you do hallway usability testing?
No. Definitely another point to review as the organization grows.
In the light of maintenance programming, I'd like to add another question to the test: do you have coding conventions?. More on this later...