3 ms·
I don't know what kind of emphasis you've seen, but being able to look at a public example of code a person has written is IMO the single biggest risk reducer a
by mightybyte 9y ago
I don't know what kind of emphasis you've seen, but being able to look at a public example of code a person has written is IMO the single biggest risk reducer available to a company hiring developers (well, other than actually having worked directly with the person before, which is an order of magnitude or two less common) because it gives me a picture of performance on real world software. Hiring is substantially about risk reduction because there's a huge amount of stuff you don't know about how the candidate will do. It would be foolish for companies to not take advantage of this potential source of signal. If it's not available, then I would proceed with my normal assessment process. Lack of public code isn't going to disqualify a candidate, but it does help to increase my confidence.
- martijn_himself 9y agoI suppose that is fair enough, and I don't think there is anything wrong with it being one of the ways in which companies assess potential candidates. From my recent experience (and anecdotal evidence) it seemed it was becoming a deal breaker for companies but maybe I reached that conclusion too quickly.
- levelist_com 9y agoIve been in the game a while now , almost 18 years - 7 as a dev, and still get asked by recruiters generally within the first or second question if i have a github profile. Nope, I moved to BitBucket. Recruiter: never heard of it, what's that? It'd be nice if tech recruiters actually had a background in tech.