> So, would it really matter if you are hiring someone who doesn't remember the difference between .call and .apply off the top of their head?
Though this posting has a lot of suggested questions, it's missing this: What should the interviewer be looking for in the answers?
In my experience interviewing candidates (not usually for dev roles), the "correct" answer isn't the only good answer. Sometimes "I don't know, but this is how I would find out" is just as valid -- and usually more telling.
Though this posting has a lot of suggested questions, it's missing this: What should the interviewer be looking for in the answers?
In my experience interviewing candidates (not usually for dev roles), the "correct" answer isn't the only good answer. Sometimes "I don't know, but this is how I would find out" is just as valid -- and usually more telling.