I like the idea... a bit concerned about the future potential that there is an expectation developers have a GitHub personal README (err "resume") tho. That's just not practical for a lot of folks either due to time, interest, or contractual reasons.
On the other hand, most profession's do have portfolio's and other mechanisms to share work with new potential employers. For some reason developer's seem to think a hiring decision should be made entirely on a a handful of 1 hour interviews conducted in a single day when their work will usually have massive direct impact on the companies product.
I think there's mostly positives to this and some downsides.
> For some reason developer's seem to think a hiring decision should be made entirely on a a handful of 1 hour interviews conducted in a single day
As opposed to... some generic profile on a central site? I don't think that is a substitute to actually talking to a candidate.
But what do I know? If I understand sites like HN correctly, talking to a person is not a good way to discover whether he/she has any skills, so maybe this is better from a recruitment standpoint. But I'm not going to create a personal profile there. For the simple reason that the words 'personal' and 'follow our format' don't go together in my mind.
On the other hand, most profession's do have portfolio's and other mechanisms to share work with new potential employers. For some reason developer's seem to think a hiring decision should be made entirely on a a handful of 1 hour interviews conducted in a single day when their work will usually have massive direct impact on the companies product.
I think there's mostly positives to this and some downsides.