Problem solving is kind of a pain for some software developers. When most programmers are given a programming problem in an interview, they make several key mistakes. The most severe of those is the improper allocation of time. If you have heard the saying "measure twice and cut once," then you are probably familiar with the idea of spending upfront time to make sure something is done right, rather than diving right in. The most common mistake I see when conducting interviews or watching someone