The Joel Test: 12 Steps to Better Code

It's almost 16 years now since Joel Spolsky wrote a blog post about "The Joel Test". I'm currently reading Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software, a book that follows a failing project and that investigates why software projects can be so difficult to get done in time, on budget and with the right functionality. It references the Joel Test. Haven't had the time to analyze it much, but at a glance I like it and think it makes sense. I'm adding it to the blog so I don't lose it.

The Joel Test

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?