|
|
|
|
|
|
by berntb
5804 days ago
|
|
|
Ahh, insight... I just assumed asking for code was stupid, since fakers could copy good code -- but I hadn't thought about the required taste in knowing what code to copy! Obvious in hindsight, you have to think like a user (here, interviewer) to understand their problems. An idea -- a web application that helps with hiring/interviewing? That is, keeps track of CVs and runs code examples through standard analysis, integrated with GMail, etc. I am obviously not competent for doing this (see start of comment :-), so take it if anyone want it. (I assume it is already done?) |
|
|
I am not saying that this would not be generally useful. In our case we're a specialised shop, without many short-listable applicants (we only ask code from candidates going forward to an interview), so it's no big deal for the tech lead to cast an eye over submitted code samples.
Not looking for perfection here - just to give you a basic example, I had a candidate submit code that did not have a single comment in it. I mean even if you wrote the code in the first place with no comments (naughty you), surely you'd stick some in before you sent it to somebody you wanted a job from, eh?
Obviously for the hotshot places that get hundreds of qualified applicants, that's a different story. Still, I think you can tell a lot about somebody's coding personality from looking at their stuff, not sure I'd trust a machine to do it.