You're right -> when you're stuck it's often a good idea to step back. I should have said "thinking clearly about the problem (which is ofter hard) can save ..

You're right -> when you're stuck it's often a good idea to step back. I should have said "thinking clearly about the problem (which is ofter hard) can save ... ". I've seen too many people writing code that "looks like it's solving some part of some problem that's similar to the problem at hand". This might actually work when the problem is ill- or undefined, but it shouldn't be the default (and only) way that software is developed.