3 ms·
> One of my interviewers told me that my answer was completely wrong just to see how I would take the criticism. I do this sometimes. A strong developer would
by yitchelle 11y ago
> One of my interviewers told me that my answer was completely wrong just to see how I would take the criticism.
I do this sometimes. A strong developer would have a good mix of defending the design decisions made and the acceptance of the errors made. This test should bring this characteristic to the forefront.
- pklausler 11y agoI think that lying to a candidate is unethical and unfair. You can get similar results without crossing that line by asking questions like "can this be made faster?" and "is this correct?", soliciting proofs of lower bounds on asymptotic complexity and loop invariants (respectively). But you shouldn't tell a candidate that their code is broken when it isn't. Interviewing is stressful and scary -- don't make it worse just because you can.
- copperx 11y ago> soliciting proofs of lower bounds on asymptotic complexity A mathematical proof on the lower bound? is that a common request and something I should prepare for in an interview?
- pklausler 11y agoIf I ask you whether your sort can be made faster, and you can make a credible case that it's O(n log n), so no, I'm happy.
- bogomipz 11y agoWow, you are just an asshole then. There's plenty of ways of having someone defend their design decision without resorting to such unethical behavior. What are you a 4 year old? What a bunch of crap. I hope that comes back to you.