News for hackers. Stuff that matters.
Re:Never judge a programmer by their commit history by whyme on Saturday February 22, 2014 @09:51AM (#7282174)
So we've gone from "Don't judge a book by its' cover" to 'Don't judge a book by its' content'?

How about don't judge anyone until having "walked a mile in their shoes"? Or even... "Don't judge".

Ideally, "before you judge...", you at least spend some time getting to know the person to find out a little more about who it is you're judging. And maybe that's really the issue.

http://www.goodreads.com/quotes/tag/judge

Re:Never judge a programmer by their commit history by MehdiKhalili on Saturday February 22, 2014 @09:55AM (#7282191)
Couldn't agree more
Re:Never judge a programmer by their commit history by erikb on Saturday February 22, 2014 @11:03AM (#7282429)
Guessing applicant quality based on evaluating the information you have about him is not judging. I can say "this guy is not a good match for our team, philosophy, and/or strategy" without saying "he is worthless"!
Re:Never judge a programmer by their commit history by whyme on Saturday February 22, 2014 @11:23AM (#7282501)
Guessing applicant quality is making a judgment of their capability, which is the core point of the article. I never suggested anyone was judging solely on a persons worth. I am suggesting that getting to know the person provides better insight in all regards.

Edit: And quite frankly hiring a programmer solely on programming capability can often lead to disastrous consequences. So if you can see some higher quality examples, it's worth investigating - IMHO.