How do they plan to work out if people are jerks or not? Or if they are looking for work, or if they work well in a team? The code itself is a major aspect to a coding job, but not the only thing.
Why Resumes and Code Screenings Are Obsolete with GitHire
71–80 of 89 posts
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#72Best of luck to these folks.
The idea doesn't suck. The current implementation might suck a little. They have their work cut out for them in any case, if for no other reason than the barrier to entry for competition seems pretty low.
They've got two huge things going for them: - $500 is right around the noise floor for a hiring process - Money co-located with mouth. If the client isn't happy, they don't get paid.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#73Earlier quoted context omitted.
> So while the quoted sentence is still true, I think anyone using this service misses out on masses of experienced developers who simply didn't publish their code on GH, for various reasons. To be fair, those are developers that most companies would be missing out on anyway.
I would bet $1 that most companies, like most developers, are not using GH. Most startups, perhaps. Most people who read HN, I don't know. Most companies, that's a pretty big basket.
And you'd be a very silly person to make that bet, as you'd lose a lot of money.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#74Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#75I searched for "Ruby" devs from my city. I search for Ruby because I know a couple of good Ruby developers and was curious if any of them popped up. And the results are pretty bad. Not only did I get awful results from other countries, the actual 2 results I got from my city are 2 devs ranked as being in the " top 20% of GitHub users by estimated expertise ". One of them has 2 forked projects with NO contributions an…
Same in my city (Toronto). I recognized maybe 4 people that I knew were good and 5 that I knew were junior.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#76So...has anyone found a profile that's NOT in the top 20% or better? If I'm in the top 20% for putting in test commits than the software dev world is in dire trouble.
I'm in the top 50%
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#77Such saucer-eyed bullshit. Many employers have moonlighting clauses that prevent employees from contributing to OSS projects. All of the companies I've worked for have. If you only go by Github commits, you'll probably be getting only a certain type of applicant and excluding most others.
Github commits might be good supplemental data to have, but if I am to do a fair apples to apples comparison between candidates who might be encumbered by moonlighting clauses, then I'll let the whiteboard coding do the talking.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#78This demand that people write tons and tons of code on our off hours is understandable but is getting, I dunno, obnoxious? If not tons , then perhaps something of very high quality. I could write a nifty little linked list implementation but would it really show that I'd be a good programmer for your particular needs? If you think it does, I predict having code written in off hours is a requirement will result in git…
I'm not even allowed to write code off hours! All my code is belong to my employer. Am I a bad hire?
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#79This demand that people write tons and tons of code on our off hours is understandable but is getting, I dunno, obnoxious? If not tons , then perhaps something of very high quality. I could write a nifty little linked list implementation but would it really show that I'd be a good programmer for your particular needs? If you think it does, I predict having code written in off hours is a requirement will result in git…
You are operating under a false assumption. That is that all public repositories (i.e. Open Source) are filled with work by unpaid volunteers. That is simply not the case for a large portion of Open Source projects (and therefore public GitHub repositories). I've been an Open Source contributor for more than a decade. I would say 90% of my open source contributions have been work where I'm extending or improving an O…
I'm not sure what you mean. I am aware that not all open source is written by unpaid volunteers but that doesn't address my central point.
If the industry demands that everyone write code, be it OSS, personal or just random junk code because they HAVE to, then github/bitbucket/launchpad/sourceforge/etc plus individual portfolios will see an inflation of sorts in code written, some of it good, most of it bad or mediocre. Let's just keep off-hours code as a bonus and not hold it against someone if it is not there. Keep fun-coding for fun! :D
Wouldn't you rather have people contribute to an OSS project because they want to, not because they feel compelled to?
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#80This demand that people write tons and tons of code on our off hours is understandable but is getting, I dunno, obnoxious? If not tons , then perhaps something of very high quality. I could write a nifty little linked list implementation but would it really show that I'd be a good programmer for your particular needs? If you think it does, I predict having code written in off hours is a requirement will result in git…
I'm not even allowed to write code off hours! All my code is belong to my employer. Am I a bad hire?
No, you're working at a bad company.