6 ms·
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
by 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