3 ms·
The interviewer made no mistake though, they made an observation; they were confused by the boolean expression. The candidate said they understood the interview
by Buttons840 2y ago
The interviewer made no mistake though, they made an observation; they were confused by the boolean expression. The candidate said they understood the interviewers concerns and was also confused, and didn't have an immediate answer. This is all normal and healthy, and something you'd commonly see in healthy and competent development teams.
The only thing I see that's wrong is that the interviewer thinks something went wrong.
- necovek 2y agoMistake: > ...the statement even though logical, is not technically right because if we start from the left cell[0][0] == cell[1][1] would evaluate to True and then True == cell[2][2] would evaluate to False given that the cell contains a char. Interviewer seemed confident ("is not technically right") which confused the candidate: > I told the candidate about the same and he agreed but he was confused at the same time Candidates are already in a high stress situation, you don't want to add to it unless you really know what you are doing (i.e. you are specifically looking for deep language mastery). Interviewer has correctly realized they've done this and learned from it: kudos to them even if too late for this candidate :)
- wiseowise 2y agoInterviewer made a mistake, stop rationalizing.
- Buttons840 2y agoBut is it "wrong" to make a mistake?
- necovek 2y agoYou said earlier: > The interviewer made no mistake though So is it wrong to admit that you made a mistake? :) And no, it's ok to make mistakes, but it is even better if we admit to them and learn from them (and the faster we do that, the better it is).