Interview gone wrong
ashu1461.com
Interview gone wrong
1–10 of 209 posts
Re: Interview gone wrong
#2Re: Interview gone wrong
#35 x == y == 10
Re: Interview gone wrong
#445 minutes interviews aren't really the place to evaluate this.
Re: Interview gone wrong
#5Re: Interview gone wrong
#6Re: Interview gone wrong
#7Stopped judging candidates on "style" due to stuff like this. I only comment if the code doesn't work, if it works i don't really bother to correct code style or provide feedback on it. 45 minutes interviews aren't really the place to evaluate this.
(But, the intent on the interviewee's part was definitely clear - I'd definitely let this pass.)
Re: Interview gone wrong
#8Also, why would you conduct an interview in a language where even if you don't know the syntax (and this is obscure) you could have looked it up or disallowed the interview to be done in Python? I think the due diligence with this issue is more to the interviewer than Python.
Re: Interview gone wrong
#9Re: Interview gone wrong
#10Python evaluates `2 == 2 == 2` to true. JavaScript evaluates the same to false. Somehow we've decided that Python is the weird one it seems.
[0] https://github.com/satwikkansal/wtfpython?tab=readme-ov-file...