31–40 of 89 posts
As best (if it works like magic even), this only gets you the cream of a small subset of engineers. But if this is the only source you would use to hire, you leave out a large pool of talent before you even begin.
The thing that could be worrying here, is that it could clutter up github with people trying to game it to get a job, instead of actually caring about the project their contributing to. It seems that in it's current state this could work very well, if this becomes a popular recruiting tool, it won't be sustainable.
Is there anywhere to submit bug reports? I looked around, but didn't see any email addresses anywhere.
How does this actually help me? I'm not going to take credit for entire projects, especially not when I'm working on them with friends.
Simple test: myself. Claims I have 5+ years of Emacs Lisp experience. Ahem, I wish. Second test: my boss. Claims he has 3-5 years of C experience (less than me, and less than he has C++ experience). Ahem. I know these are estimates, but it highlights the flaw: it just looks at your repos and has no insight what's happening. Maybe it would work better if it could detect if your patches are actually being pulled by ano…
But, I learned Ruby in May 2008, because I got a job doing Rails development. (I just looked it up). So, 3 years, going on 4.
If you think it does, I predict having code written in off hours is a requirement will result in github being flooded with just horrible code. It's hard to evaluate code in a quick glance. Let's keep it as a bonus type thing so the pressure won't be so high to produce just anything, to torture a text editor until it gives something that pleases the eye and sleights the mind.
Please, keep the industry from moving to make this sort of thing a requirement. I write crappy code in my spare time for fun not because I think it'll get me hired.
----
Not everyone can write code for 50 hours a week and then 10+ more at home, especially if they have outside interests, a family or are just plain tired of it.
Writing code in spare hours is neat, and I do it myself, but I think it needs to be seen as a bonus, not as a requirement.
Perhaps employers are wanting to hire burn-out proof people. I don't think there are enough programmers on the planet to meet employer's demands to hire the best. The implication of wanting 'the best' and asking for code in off hours is that if you don't write code in off hours, you are not the best and not worthy. It's thinly veiled and having been through a few interviews (sometimes I showed them code I had written in off hours, sometimes not) recently, my experiences are probably anecdotal but it makes me wonder.