[paydro]

I think it should be a combination of both GitHub and StackOverflow. GitHub is great to see if the person can code, and a very crucial part of hiring. StackOverflow is great to see if a person can communicate, which I think is as important as having the ability to code.

I've come across many programmers that can code well, but had horrible communications skills. It's always difficult to interact with these programmers. I spend more time extracting the meaning of what they're saying rather than getting work done.

[blasdel]

StackOverflow primarily exposes their addictive game-playing, not their communication skills. The rep/badge bullshit encourages inane responses, and the wiki aspects cover the tracks.

[robryan]

It seems to be more about the detailed and correct answer voted up the most that you find from searching something on Google, for that it works really well, not being part of the community there I don't care about that other 10 half assed replies for badges/points

[blasdel]

They have a very visible group of users that post a no-assed answer as fast as possible and start doing the same google searches the asker did to pad out their answer. Their bullshit answer will be at the top initially, so they'll have the means to cannibalize the knowledgeable users who follow.

[jamesbritt]

"StackOverflow is great to see if a person can communicate ..."

... on StackOverflow.

Meanwhile, the great bulk of programmer communication is happening on blogs, mailing lists, and IRC.

You're very right that written and verbal communication is important, but you have to look in the right places for it.

[jrockway]

The reality is that many people cannot communicate anywhere, so if they are writing good stuff on Stack Overflow, they are probably going to have some ability to explain to their team how their code works. (But it also means that they are the type of person who is happy to waste an hour replying in detail to some dumb person on the Internet.)

[clutchski]

GitHub showcases communication skills via project documentation (the documentation for bottle[1] is great), commit comments (kangax[2] often has concise, prescient suggestions for changes), and the like.

[1] - http://github.com/defnull/bottle/ [2] - http://github.com/kangax