3 ms·
Agreed. Every single time I've ever looked at a github profile for a candidate they've had 1 or 2 original repositories that are as bare bones as possible and 1
by malyk 9y ago
Agreed. Every single time I've ever looked at a github profile for a candidate they've had 1 or 2 original repositories that are as bare bones as possible and 18 forked repositories so it "looks" to the untrained eye (i'm guessing recruiters) that they have an active profile.
- Vendan 9y agoAnd then you have others with 90+ repos, and 75%+ of them are original code, and have thousands and thousands of lines of code. Maybe all your candidates have been weak/just out of school. Also, forked repos are fairly obvious, and there's a dropdown to just show source repos, and if they are manually forking to prevent it from showing as a fork on there, that's a pretty shady indicator that you may want to follow up on...
- gaius 9y agoThose candidates are 1 in 100, seriously. If you have a stack of CVs to filter, it literally is not worth looking at everybody's Github to check. Just filter by formatting and spelling and you're probably good.
- Vendan 9y agoAnd that's why I think resume based hiring is shit, cause my resume isn't great, but my github and skills are stellar. But people like you would chuck my resume in the trash without thinking twice cause I'm not currently working as a programmer.
- gaius 9y agoIf that's true, the target of your blame should be the weak candidates who flooded Github with junk repos. And/or whichever journo or blogger started telling those people that "having a Github" was a shortcut through the hiring process.