I've only been interviewing for a few years so I don't have a large statistical sample, but I can tell you that within a few minutes I can usually only tell if they think like me or not. The rest of the interview determines if they can code regardless of my biases, and can actually get stuff done.
> within a few minutes I can usually only tell if they think like me or not. The rest of the interview determines if they can code regardless of my biases
If they don't ask for relevant details, etc, they won't be coming up with a solution no matter how they do it.
Comments
Probably in the context of the grandparent so assured that he knows how to assess programmers' abilities within 5 minutes.
Not five minutes. Two minutes. Sometimes less. And you should, too.
I've only been interviewing for a few years so I don't have a large statistical sample, but I can tell you that within a few minutes I can usually only tell if they think like me or not. The rest of the interview determines if they can code regardless of my biases, and can actually get stuff done.
> within a few minutes I can usually only tell if they think like me or not. The rest of the interview determines if they can code regardless of my biases
If they don't ask for relevant details, etc, they won't be coming up with a solution no matter how they do it.