3 ms·

The Joel Test : https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s..

The Joel Test : https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s... * 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?

wyldfire 6y ago
Joel included this in the SO jobs site. I wonder how many employers lie to themselves about the answers to these questions. In any case, questions like these are great ones to ask during an interview. Companies with poor process will be pretty frustrating to work at.
lojack 6y ago
I think this is super helpful, I definitely don't think all scores on the Joel test are equal. I would steer very clear of a company that had an 11 on the Joel test because they didn't use source control, but would happily work at a company with a score of 8 because they allowed some bugs, didn't have dedicated testers, no hallway usability testing, and had to take a few steps to build.
raverbashing 6y ago
Joel's test is a good baseline. Ok, some things might or might not apply in some cases (are you really not going to put out a feature before fixing a minor low priority bug?), and I've seen companies follow these items but still be atrocious places, anyway. My point is: a lot of software wasn't built using these principles. Software that's used in a lot of places and/or got very popular (also note there's no "unit tests" in those items) So yeah, these are all good, but what I would set as priority (in my mind) - Source control - Quiet/comfortable working conditions (the "best tools" might be merged here - though the meaning of best tools is debatable) - Bug database - One step build - Candidates writing code on interviews
LandR 6y ago
Jeez Do you use source control? YES Can you make a build in one step? NO Do you make daily builds? NO Do you have a bug database? NO Do you fix bugs before writing new code? NO Do you have an up-to-date schedule? NO Do you have a spec? NO, NEVER. Do programmers have quiet working conditions? YES Do you use the best tools money can buy? NO Do you have testers? NO Do new candidates write code during their interview? NO Do you do hallway usability testing? NO
kodablah 6y ago
Unfortunately this test lets absurdly low quality code pass. While code quality can be subjective on the margins, general poor quality code is obvious to most.

wyldfire 6y ago

Joel included this in the SO jobs site. I wonder how many employers lie to themselves about the answers to these questions. In any case, questions like these are great ones to ask during an interview. Companies with poor process will be pretty frustrating to work at.

lojack 6y ago

I think this is super helpful, I definitely don't think all scores on the Joel test are equal. I would steer very clear of a company that had an 11 on the Joel test because they didn't use source control, but would happily work at a company with a score of 8 because they allowed some bugs, didn't have dedicated testers, no hallway usability testing, and had to take a few steps to build.

raverbashing 6y ago

Joel's test is a good baseline. Ok, some things might or might not apply in some cases (are you really not going to put out a feature before fixing a minor low priority bug?), and I've seen companies follow these items but still be atrocious places, anyway. My point is: a lot of software wasn't built using these principles. Software that's used in a lot of places and/or got very popular (also note there's no "unit tests" in those items) So yeah, these are all good, but what I would set as priority (in my mind) - Source control - Quiet/comfortable working conditions (the "best tools" might be merged here - though the meaning of best tools is debatable) - Bug database - One step build - Candidates writing code on interviews

LandR 6y ago

Jeez Do you use source control? YES Can you make a build in one step? NO Do you make daily builds? NO Do you have a bug database? NO Do you fix bugs before writing new code? NO Do you have an up-to-date schedule? NO Do you have a spec? NO, NEVER. Do programmers have quiet working conditions? YES Do you use the best tools money can buy? NO Do you have testers? NO Do new candidates write code during their interview? NO Do you do hallway usability testing? NO

kodablah 6y ago

Unfortunately this test lets absurdly low quality code pass. While code quality can be subjective on the margins, general poor quality code is obvious to most.