Ask HN: Advice for when thinking about a problem for longer than is needed
Hello there!
I've started to examine my approach to solving problems in both design and development. This caused me to notice that I often spend a lot more time thinking about, and around a problem than is actually required to solve the problem, or at least get started on it. I'm curious to hear what your perspectives and advice is for dealing with this.
I can't tell if it is that I find thinking about the problems more entertaining than solving them. Or if that I use this pondering time as a form of procrastination. It feels productive, but ultimately, most of the time, this pondering doesn't lead to any more break throughs or ideas than actually writing a solution.
What are your thoughts? Have you faced this before? To mimic a famous stoic quote: God, grant me the insight to discover the optimal, diligence to work on the feasible, and wisdom to know the difference. You clearly have the first. What do you think you miss? The second or the third? Thanks! I appreciate the adaptation of the quote. I probably need to be more diligent in working on the feasible. I think my default is to assume everything must be optimized, and not that everything could just ‘be done’. > I think my default is to assume everything must be optimized, and not that everything could just ‘be done’. This is a number 3 problem.