Re:On Hiring: How Not to Annoy Developers
by akavi on Thursday January 26, 2012 @05:15AM
(#3513531)
Having never experienced it, can someone tell me what the point of having the applicant code on a whiteboard instead of on a computer is (Maybe with screen-sharing so the interviewer doesn't have to be looking over the applicant's shoulder)?
[ Parent
| on HN ]
It really depends what you are testing for, but using a whiteboard lets you get away from the details of things like syntax errors and language particulars and let's you focus on solving a problem at a much higher level of abstraction. Basically it comes down to, do you want to see if the person can write good Ruby code (use a computer) or to you want to see if a person can come up with clever abstract algorithms to solve hard problems (use a whiteboard).
Re:On Hiring: How Not to Annoy Developers
by ejgejg on Thursday January 26, 2012 @07:39AM
(#3513855)
But I come up with all my clever abstract algorithms in the shower - usually while I am thinking of something else. I don't think being "clever" on demand is the mark of a good developer. I would prefer they look at some of my available open source code - that gives a much better reflection of my abilities.