Re:Ask HN: "a piece of code you're proud of" - what does it ...
by RiderOfGiraffes on Sunday September 12, 2010 @12:35PM
(#1683945)
Anything done on paper/email could be the work of someone else. The first thing we then do in interview is give the person a disk-less, internet-less machine and get them to write FizzBuzz. As they do it we get them to talk about their usual dev environment.
Once they've done that we move on to discussing the code they sent.
All these things are purely to weed out the complete time-wasters. From the remainder, we then try to find someone who can design, code, document and collaborate.
Re:Ask HN: "a piece of code you're proud of" - what does it ...
by anthonyb on Sunday September 12, 2010 @08:02PM
(#1684928)
No, because in the follow up (either telephone or face-to-face) you're normally asked questions about the code (I do, anyway). It's incredibly easy to spot people who've cut+pasted something and have no idea how it works - just ask them why they did it a certain way, or what tradeoffs they made, and watch them squirm...
This does make sense if you'd ask him to explain it at the interview, but then the applicant can also give context and explain why he thinks it's good code.