A while back—the year 2000 to be exact—Joel Spolsky wrote a blog post entitled: “The Joel Test: 12 Steps to Better Code.”
Many software engineers and developers use this test for evaluating a company to determine if a company is a good company to work for.
In fact, many software development organizations use the Joel Test as a sort of self-test to determine what they need to work on.
Here is what the Joel Test looks like, in case you aren’t familiar:
The Joel Test
- Do you use source control?
- Can you make a build in one step?
- Do you make daily builds?
- Do you have a bug database?
- Do you fix bugs before writing new code?
- Do you have an up-to-date schedule?
- Do you have a spec?
- Do programmers have quiet working conditions?
- Do you use the best tools money can buy?
- Do you have testers?
- Do new candidates write code during their interview?
- Do you do hallway usability testing?