33

Me (experienced java dev) in an interview..

C: „what’s the difference between equals and equals equals and equals equals equals in js?“
Me: *i explained it perfectly*
C: „what’s the difference in Java between equals and equals equals and dot equals?“?
Me: „sorry, I don’t know. I’ve never ever seen .=„..

About 15 min after the interview, I was like: „holy moly fucking shit, please shoot me.. he meant .equals.. not .=....

For the devs: I‘M FUCKING STUPID!!!!

For the beginners: THATS the importance of „context“!

Comments
  • 2
    foo.equals()
    not
    foo.=bar

    If someone has problems with visualization of what's going on.
  • 5
    Sounds more like an imbecile of an interviewer who was intentionally trying to trip you up with misleading context conditioning. Probably has a background in used car sales and thinks they are soooo clever for incorporating this into their interviewing technique.
  • 3
    You're not, I also thought puzzlingly .=?🤔
  • 4
    Actually got the position after all.🤟
Add Comment