Finding exceptional talent on GitHub certainly a solvable problem, but the real challenge for GitHire is the one you can see immediately when you pull up this page: http://githire.com/order In the first few reloads, I've seen John Resig, David Heinemeier Hansson, and Yehuda Katz pop up. Maybe they're free to do a quick phone screen? Here's hoping that there's a lot of secret sauce keeping companies from trying to dat…
Why Resumes and Code Screenings Are Obsolete with GitHire
51–60 of 89 posts
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#52From my estimated experience: CoffeeScript: 5+ years Ha ha. (the language has been out for 3 years, became known maybe year after release)
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#53Earlier 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.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#54This 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 like your opinion (probably because I'm biased of this trend as well). Unfortunately, we live in the world where people eat people. For those who have large number of repos and code written in GitHub, they would rejoice when they see this. Just like Haskell people would feel excited when they see the number of jobs for Haskell programmers out there cannot be met with the supply. These people will push this idea for…
I'd be up for changing the world so people stop eating each other.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#55I 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…
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#56Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#57I know more than a handful of exceptional engineers who don't even have GitHub accounts. And I know a few really average engineers who are active on GitHub. 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.
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#58Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#59Why is my python professor Hireable: false?
Re: Why Resumes and Code Screenings Are Obsolete with GitHire
#60On the search page, how do they determine "Hireable"? And why is mine true? Why is my python professor Hireable: false?