jwingy
Joined 15 years ago
Joined 15 years ago
*edit looks like the article has a convenient link to another article talking about this exact problem:
http://www.vox.com/2016/2/12/10970858/flattening-duck-curve-...
That being said, I feel like the author is confusing a bit the specific implementations of modern APIs vs the concept of an API which I see as simply some (somewhat standardized) interface to a system which you don't own. Those seem like two different problem domains to me, but perhaps I'm arguing over a different definition of APIs than from what the author is talking about....
There's definitely value in asking a candidate questions face to face as there are times when problems need to be discussed, but clearly there's a non-trivial segment of the programmer population that has trouble performing under this type of atypical situation.
Why not also have a sort of "written test" portion of an interview where the candidate doesn't have to stress out about performing in front of people they don't know? It would certainly help reduce the flagging of false negatives.
EDIT: by "written test" I mean something like a test where the questions are on a piece of paper or text file, and the interviewee just answers it on there, without another human sitting there and staring at them. The interviewee can always be asked to explain his/her answers afterwards.