Earlier quoted context omitted.
FWIW, I'll look at a candidate's Github account whenever they list it on their resume. That doesn't mean I'll bring it up during the interview unless there was something particularly interesting to talk about. It's pretty useful for screening candidates, especially looking at code written <1 year ago. I do keep in mind that code written in free time might not have the same standards as production code, but often ther…
You realize that github dates can easily be falsified, right ? Besides, you are only using this as a negative ? So you'll actually hire people who don't put in extra effort over people who put slightly substandard free time code online ? That seems like a losing strategy. I've always found that willingness to put in effort vastly outperforms ability. Not to an infinite extent, but quite a bit.
Yea, but why would someone bother in this case?
>Besides, you are only using this as a negative ? So you'll actually hire people who don't put in extra effort over people who put slightly substandard free time code online ? That seems like a losing strategy.
That's not what I said at all. It's potentially a positive or a negative, just like anything else on a resume. I've seen plenty of Github profiles that have files with 2000 lines of spaghetti code and no structure or testability. Just like I've seen profiles with neat projects and excellent code.
>I've always found that willingness to put in effort vastly outperforms ability. Not to an infinite extent, but quite a bit.
I agree with this in general too.