3 ms·
How could you verify the code is actually theirs in just one hour, and not something they've been coached on? The stakes are so high that we already have an awf
by prodigal_erik 13y ago
How could you verify the code is actually theirs in just one hour, and not something they've been coached on? The stakes are so high that we already have an awful lot of blatantly unqualified people trying to bluff their way through in-depth interviews, and making that easier is a huge step backwards.
- kanzure 13y ago> How could you verify the code is actually theirs in just one hour You don't have to review the code inside of one hour. You can take as long as you want on that. The point was that when talking with them either on the phone, in person, whatever, you take only an hour. Code review can take as long as you please. I highly encourage you to look at source code before making a hiring decision.
- freework 13y agoIts usually pretty damn obvious Ask them to explain what the code does and why they wrote it. If they backpedal and aren't able to say anything then you can assume they didn't write it.