@heyrhett, did you already win some customers? Anyone purchased your 500USD package?
Why Resumes and Code Screenings Are Obsolete with GitHire
81–89 of 89 posts
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#82Earlier quoted context omitted.
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.
I'm quite certain that most companies do not use GH. The number is probably close to 1% (of tech companies).
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#83Earlier quoted context omitted.
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.
You absolutely do not have enough context to make that judgement. I doubt his company is curing cancer or colonizing mars, but do you really think poor intellectual property assignment policies alone make any company, bad? It is one of many, many axes and it doesn't override everything else.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#84http://githire.com/best : you guys should check if they are actually human beings, (as much as you would like to hire him, android is not a real person).
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#85This 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?
If your company is dictating what you do when you're not working you either need to find out if those clauses are even binding (probably not) or just find a modern place to work. If they really control what you do when you're not on the clock then explain to me how you're not a slave.
The worst part about this is, if companies are allowed to do this they can ensure that some people must continue working for a living instead of becoming financially independent through their own talent.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#86Earlier quoted context omitted.
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 medioc…
I'm not entirely disagreeing with your argument, but isn't it kind of like saying "if the industry demands that people write job applications to get a job, they will be flooded with bad applications"? While that's true, it doesn't change the fact that you need data to evaluate applicants on. I don't see how people will think that writing crap code will improve their chances.
Besides, there is absolutely no difference between "counting something as a bonus" and "not holding it against someone". Hiring is a zero-sum game, your advantage is necessarily the others' disadvantage.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#87I don't see public repositories as being a 100% indicator. The information they provide is useful, but I still want to do a whiteboard interview with candidates. There are a few reasons for this. Most of my personal projects are much simpler than what I get paid to do. Many of my repositories contain lots of good code written by other people and it's unfair for me to take credit for their work. I like the whiteboard…
You must have a more interesting job than me. Most of my personal projects are way more complicated than what I get paid to do.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#88Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#89Biggest problem here is that the majority of the code I write is not open source, and OSS code I write is very very different than the code I write professionally (so that my employer has no claim on it), so the github version of me is nothing like the real version of me.