4 ms·
Sounds good, but couldn't the applicant just copy code from the internet which he heard was good code? It doesn't prove he can write code. This does make sense
by relix 16y ago
Sounds good, but couldn't the applicant just copy code from the internet which he heard was good code? It doesn't prove he can write code.
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.
- RiderOfGiraffes 16y agoAnything 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.
- code_duck 16y agoI suppose, if you want to be disqualified for plagiarism. No different than handing in someone else's work for college.
- ams6110 16y agoI'd assume that anyone receiving code "from the internet" could quickly determine this was the case with a few minutes' time on Google.
- anthonyb 16y agoNo, 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...