3 ms·

I have been working in C# for 2 weeks, and Googled this last week. I think it's kinda the difference between being interested in making things work, and underst

by dtech 12y ago

I have been working in C# for 2 weeks, and Googled this last week. I think it's kinda the difference between being interested in making things work, and understanding how the language works.

UnoriginalGuy 12y ago
It is also that moment of self doubt. You assume there "must" be a difference since the interviewer implied there is, so in order to contradict the interviewer (or call them "wrong") you have to be 100% sure. I'm sure many people would prefer to get the wrong answer in interview than imply the interviewer's premise is wrong. That's why trick questions are dumb in interviews, they ignore the power dynamics in play and how someone will be judged if they seemingly "fight the interview process" (by calling the question(s) flawed). In normal conversation I'd likely call it an alias (without 100% certainty) but in an interview I'd prefer to be wrong than to imply the interviewer's question is flawed. TL;DR: All the blogger proves is that they're a bad interviewer, not that they're interviewing bad programmers.