Wednesday, October 28, 2009

12 Steps to Better Code (by Joel Spolsky)

According to Joel Spolsky we can ask ourselves couple of simple questions in order to decide how good our team is:

1. Do you use source control?
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?

The nice thing about this test is that it's easy to get a quick yes or no to each question.

Give your team 1 point for each "yes" answer.

A score of 12 is perfect, 11 is tolerable, but 10 or lower and you've got serious problems. The truth is that most software organizations are running with a score of 2 or 3, and they need serious help, because companies like Microsoft run at 12 full-time.

Of course, these are not the only factors that determine success or failure: in particular, if you have a great software team working on a product that nobody wants, well, people aren't going to want it. And it's possible to imagine a team of "gunslingers" that doesn't do any of this stuff that still manages to produce incredible software that changes the world. But, all else being equal, if you get these 12 things right, you'll have a disciplined team that can consistently deliver.

You can read the complete Joel's post here.


1 comment:

  1. Our team got 10/12 in Joel test! could easily become 11 (with visualBuild, daily builds are just a matter of desicion).
    The 12 is a bit of a one is wondering in the hallways ;-)