3 ms·
Because, as devil's advocate, most programming candidates can't write FizzBuzz in a single programming language. I know I can program. You don't know I can pr
by reificator 9y ago
Because, as devil's advocate, most programming candidates can't write FizzBuzz in a single programming language.
I know I can program. You don't know I can program. Do you want to hire someone who simply can't write a line of code to save their life and then have to deal with the headache of firing them and hiring someone else?
And that's best case scenario, because someone who can't code can do a lot less damage than someone who can code badly.
False negatives suck for the employee because they don't get a job. False positives suck for the employer because it's a massive headache and money sink. Since employers are the gatekeepers, they're often going to try to minimize false positives, even at the cost of false negatives.
- cozuya 9y agoThere's lots of other ways to "find out if people can program" than the above nonsense. The easiest is if they have any open source projects.
- reificator 9y agoResuming my role as devil's advocate: How do you know they wrote them? How do you know I didn't write your new candidate's project for them? And it should be asked, why is spending hours and hours building open source software outside of your day job a reasonable requirement? Doing open source well is incredibly difficult and requires a different skill set than working as a developer. If you want to sit in front of a computer for several hours, then go home and do it all over again for free for the community, that's great. Sincere thanks are in order for that. But requiring it from all your candidates is unreasonable IMO.