"there's no correlation between skill level and having a GitHub repo"
There may be no evidence of any correlation, but I'm willing to bet there's no evidence in favor of a lack of correlation, because I'm pretty sure no one has done anything approaching a scientific study on this.And if you count Google Code, Bitbucket, Sourceforge? Github alone has "2.1 million users hosting over 3.7 million repositories". What's your source for your statistic?
> When all of your work is online, it suggests you are not spending much time contributing value to whoever is employing you.
Or that you enjoy writing code so much that you do it in your free time.
> Companies that can't find developers often have bizarre and useless criteria such as "must have GitHub repository" ... none of which is correlated with ability.
Source?
That said, if you're a Rails developer and you don't have a Github account, I'm still probably not going to read your resume.
>> not having a Github account at all would be kinda weird these days
and this ...
>> if you're a Rails developer and you don't have a Github account, I'm still probably not going to read your resume.
Thanks for the heads up hansef.
What's the business need for stating it in those terms, then?
It's not about requiring everyone who works for us to be a 23 year old with no family or life who spends every night hacking on shit, just about a baseline standard for community engagement. Lack of Github account with some level of activity (even if that's just starred repos, forks, etc) is a pretty strong indication someone wouldn't meet that level of engagement, and so wouldn't be a good match.
Bingo (at least for me). Both companies I've worked for require you to submit a proposal to an open source review board for approval. I went through the process at my previous job and approximately 2 months later I was given the go-ahead. Not worth it.
I scoffed at this article for being too hopeful.
This is silly. I interview plenty of people who can barely code.
If someone has interesting projects on github, I'm reasonably confident they can code. Hence, correlation between having projects on github and coding ability.
Evaluating a github repo, while nonsimple, is far more accurate than scanning a resume.
It definitely depends on the culture of different companies - for example, I work in finance and my day-to-day work is proprietary and not for public consumption, but my strange personal side projects wind up in bitbucket or github.
Probably less than 1% of developers have GitHub repos and there's no correlation between skill level and having a GitHub repo.
If you have extensive and current open source contributions, for most people it means you're unemployed, or you're violating your employer's contract terms.
Evaluating a GitHub repo for a summary of skills in not a trivial task, as scanning a resume is.
When all of your work is online, it suggests you are not spending much time contributing value to whoever is employing you.
Companies that can't find developers often have bizarre and useless criteria such as "must have GitHub repository" or "must have LinkedIn" or "must have FaceBook", none of which is correlated with ability.
We hire lots of capable people without GitHub repositories.