in the last post I mentioned a good reference to prepared youself for a interview process. However, before you get prepared, you need to choose the company that you’ll work for. Actually, this is one of the hardest step to take. I don’t know anyone who wants to work for a bad company or within a poor team. But, how to measure the quality of the company if you don’t even know anyone from there?
This month I’ve read Joel Spolsky blog a lot and in one of his posts he talks about measuring how good a software team is. For that, he created The Joel Test: 12 Steps to Better Code. The test is shown below.
With The Joel Test it’s easy to answer ‘yes’ or ‘no’ for any of those questions. For each ‘yes’ answer you count 1 point and as Joel says “A score of 12 is perfect, 11 is tolerable, but 10 or lower and you’ve got serious problems”.
To take profit from The Joel Test, he gives some warnings on how to use it:
- Rate your own software organization.
- If you’re the manager of a programming team, use this as a checklist to make sure your team is working as well as possible.
- If you’re looking for a programming job, ask your employer how they rate on this test.
- If you’re an investor doing due diligence to judge the value of a programming team, the test can provide a quick rule of thumb.
If you work in a team with score lower than 10, it’s time to wake up. Try talking with you manager on how to improve your team score or, if you’re only a grunt, this another Joel’s post may help you. You can take more information about The Joel Test in his own post dedicated to it.