I do that; I ask candidates to code in notepad instead of an environment where you an compile, and it's intentional. Failure come in three types - bad understa

I do that; I ask candidates to code in notepad instead of an environment where you an compile, and it's intentional. Failure come in three types - bad understanding (failure to understand the problem), bad planning (plan doesn't actually solve the problem), and bad implementation (failure to implement the plan correctly). The third type includes typos and off-by-one errors that I don't want the candidate to get hung up on. I might ask about an issue if I spot it, but if not I'd rather keep going on the more relevant parts of the solution. Also, you can leave part of the solution in pseudocode without getting distracted by a bunch of squiggly underlines, and handwave away parts of the problem that we don't care about.