4 ms·
Very interesting question because once you solve it, it doesn't seem hard anymore.
by fitba1969 8y ago
Very interesting question because once you solve it, it doesn't seem hard anymore.
- seanmcdirmid 8y agoYa, I hate this question as an interview one. I’ve solved lots of hard problems, but only the ones I haven’t solved yet stick around in my head. It’s even worse if they aren’t interested in design problems, but rather technical ones.
- jamestimmins 8y agoHa, this is actually why I thought to ask it. Sadly, "I read the docs and wrote sample code for days until it became obvious" isn't what interviewers are looking for.
- seanmcdirmid 8y agoI know, but I debugged a lot of use cases, tried to narrow the scope of the bug, thought really hard about the execution in my head, and then fixed it all using an explicit semicolon.... Asking an experienced dev this question is like asking someone what was the hardest food they had to eat and how did they manage to swallow it. What is the interviewer hoping to learn by that?
- yetihehe 8y agoIt's a simple task to check that you really are experienced developer and not someone who stuffed his CV.
- seanmcdirmid 8y agoIt’s one of those questions you should definitely ask yourself before you ask others, to check if a reasonable answer is possible or not.