One habit that I think is important, and often overlooked, is to be able to break out of a mindset and questioning yourself with: "Am I solving the problem at

One habit that I think is important, and often overlooked, is to be able to break out of a mindset and questioning yourself with: "Am I solving the problem at the correct level, using the appropriate method/technique/tool? Don't forget the big picture" It's easy to just keep coding and add to existing code, architecture and methods. But sometimes the frog is starting to boil. Better then to re-evaluate whether to do some major refactoring, or add some layer of abstraction to keep it maintainable. Sometimes you need to recognize that you're merely treating symptoms rather than a underlying problem. Sometimes you need to recognize that there are some library/tool/algorithm etc that can eliminate the need to solve a problem yourself.