I'm talking specifically about interviews here. (In short, yes one should be able to think about programming problems while away from the computer. However, on

I'm talking specifically about interviews here. (In short, yes one should be able to think about programming problems while away from the computer. However, one doesn't arrive at a solution away from the computer. Napkins don't compile.) Writing code in an interview will tell you one of two things: 1. This person has encountered the problem before and is simply regurgitating the solution they came to when they had four months to work on it and the assistance of a TA and other students. 2. This person has not encountered the problem before. While the latter case is considered ideal, it only works if you know how to ask the proper questions. I suggest avoiding it because there are more direct ways to get what you want to know. My suggestion? Code reviews. Have some pre-made examples or ask the candidate to bring their own code. No one has to be put on the spot. It's much easier to control the dialog.