4 ms·

Those "stupid programming puzzles" are about evaluating problem-solving abilities. Asking about architecting a system from a higher level also does this. Asking

Those "stupid programming puzzles" are about evaluating problem-solving abilities. Asking about architecting a system from a higher level also does this. Asking how a browser works is in the memorization category, and I just don't understand how that can give you useful information. Now you didn't give a lot of details - maybe you're upset about being asked to implement mergesort. That would also be an exercise in memorization. I'm not condoning that. Being able to analyze an algorithm from a time/space complexity standpoint is about whether you can reason about code. I think that is also a useful thing to find out in an interview.

berntb 14y ago
To answer how to get an URL in detail would need understanding of the 7 layers of OSI, sockets, http/ftp/etc, SSL, html layout, keepalive, etc etc. The answer should be a really informative about how much someone understand (and check architecture grokking). [Edit: I might try this, thanks!] Cons are: It is specific to web people, of course. And not really a programming question.
- tetha 14y ago
  On the other hand, it's a good question to see how someone handles limited or lacking knowledge, because knowing everything about an HTTP request down to the wire is hard. There is just so much going on in that stack by now.
- typicalrunt 14y ago
  true, it is not about programming, but how much programming does a programmer do? this is over a phone interview and I hate asking actual "type this code" in phone interviews. The way I view this question is the way I view, say, a carpenter. A carpenter must know the different types of wood, the milling technique, etc. Of course, they don't need to know it to any great extent, but have a rough idea because in the course of their work they might come across something new to them, and need to rely on the fundamentals.

berntb 14y ago

To answer how to get an URL in detail would need understanding of the 7 layers of OSI, sockets, http/ftp/etc, SSL, html layout, keepalive, etc etc. The answer should be a really informative about how much someone understand (and check architecture grokking). [Edit: I might try this, thanks!] Cons are: It is specific to web people, of course. And not really a programming question.

tetha 14y ago
On the other hand, it's a good question to see how someone handles limited or lacking knowledge, because knowing everything about an HTTP request down to the wire is hard. There is just so much going on in that stack by now.
typicalrunt 14y ago
true, it is not about programming, but how much programming does a programmer do? this is over a phone interview and I hate asking actual "type this code" in phone interviews. The way I view this question is the way I view, say, a carpenter. A carpenter must know the different types of wood, the milling technique, etc. Of course, they don't need to know it to any great extent, but have a rough idea because in the course of their work they might come across something new to them, and need to rely on the fundamentals.