News for hackers. Stuff that matters.
Re:Interviewing programmers: coding test example explained by tptacek on Thursday June 03, 2010 @01:27PM (#1401904)
His logic is that you are in fact "dinging" the candidate. He used an artificial scenario to illustrate that.

In reality, you never have two candidates who are absolutely equivalent except for spelling ability. The interview process is extremely high-error, brutally timeboxed, and infamously ineffective. The most important capability you need to assess is "ability to code". You know a priori you're going to do a crappy job assessing that capability.

Whether or not he thinks you should be wasting time on trivialities like variable name spelling (I myself would dodge this problem by using names like "x" and "cp" for utterly trivial, well-known example problems like this), I don't know. My bias is pretty clear.

Re:Interviewing programmers: coding test example explained by roel_v on Thursday June 03, 2010 @01:45PM (#1401946)
Let's clarify terminology first - I shouldn't have used the word "autoding" because it's slang and its use in another message board that I visit may not be universally accepted. I meant "an automatic disqualifier" - a condition that would completely negate any positive aspects.

Under that definition, I don't see any way to construe my earlier remarks as meaning that I would such a high importance on spelling of variable names.