2 ms·
This isn't about rejecting bad programmers — it's about rejecting good ones. If you can't afford a bad hire, that means you should spend more time and care tryi
by chc 16y ago
This isn't about rejecting bad programmers — it's about rejecting good ones. If you can't afford a bad hire, that means you should spend more time and care trying to determine accurately whether somebody is good rather than relying on a rough heuristic with a strong negative bias — especially if you find that your heuristic is rejecting everybody.
- sghael 16y agoyou make a valid point, and i completely agree. It's about more efficiently honing in on the best candidates. And the trick is to do that early in the process, especially when the hiring process is typically front-loaded with mostly crap candidates. I've thought A LOT about this problem... so much so that my web-startup is attempting to solve one aspect of this problem (see my HN profile for the link).