Eventually, I settled on a list of questions I would ask myself for each problem as it arose. I found that asking these questions, in order, helped me make the best decision possible:
1) Is this really a problem?
2) Does the problem need to be solved?
3) Does the problem need to be solved now?
4) Does the problem need to be solved by me?
5) Is there a simpler problem I can solve instead?
We've talked about what it takes to be a senior developer before, and I'd say this kind of thinking should be on that list as well.
Direct Link to Article — Permalink
The post How I think about solving problems appeared first on CSS-Tricks.