3 ms·
> people who actually could prove they had done work went to the head of the line Isn't that usually sorted out by the resume piece of the puzzle? By listing p
by prawks 13y ago
> people who actually could prove they had done work went to the head of the line
Isn't that usually sorted out by the resume piece of the puzzle? By listing placed an applicant has actually worked?
I know it's not your full hiring procedure you've outlined here, but I just see that kind of filtering as very naive. You'd have to make a huge number of assumptions to go from someone's OSS contributions to anything about their work ethic.
- tokenrove 13y agoUnfortunately it's easy to make claims on one's resume that are hard to refute. Yes, you worked there, but what did you actually do? What did the code you wrote look like? Every writer who advocates FizzBuzz or something related has specifically mentioned these are candidates with resumes that got them to the interview stage, but who couldn't actually write code. Looking at open source code or a portfolio is an extension of that, since one doesn't really have time in an interview to do anything more complex than FizzBuzz.
- icelancer 13y ago>Isn't that usually sorted out by the resume piece of the puzzle? By listing placed an applicant has actually worked? You clearly haven't done a lot of hiring if you think this is a good filter. People lie.