> how do you know I didn’t copy the code from somewhere?
You can ask your candidate to explain the code... Is that not obvious?
> writing code for the sake of writing code doesn’t tell a hiring manager if the person can take requirements and translate that to an automated process
Kind of sounds like you don't know what open source software is.
> excuse my language, shit out code for the sake of appearing productive
I won't excuse your language. You sound like you're part of the problem buddy. I don't think you have any idea how to evaluate a programmer.
> You can ask your candidate to explain the code... Is that not obvious?
Asking about projects is the obvious thing, but only substantial and interesting projects really provide any interview value. Yet another Todo app doesn’t fit that criteria. Neither is another scaffolded crud app.
A PR to fix a bug in a semi-popular library is worth. But saying “I have a lot of repos” is def not.
I don't know why you're assuming my or most good programmers' githubs are filled up with todo apps and other worthless garbage.
> saying “I have a lot of repos” is def not.
When did I say that? I didn't. They should be looking at the repos and asking about them, not just taking your number of repos and using that as some kind of metric.
You can ask your candidate to explain the code... Is that not obvious?
> writing code for the sake of writing code doesn’t tell a hiring manager if the person can take requirements and translate that to an automated process
Kind of sounds like you don't know what open source software is.
> excuse my language, shit out code for the sake of appearing productive
I won't excuse your language. You sound like you're part of the problem buddy. I don't think you have any idea how to evaluate a programmer.