LegoZombieKing

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?

I have been building and working on a passion project of building small functional web apps[0] for the past year and a half. Within the past few months I have been learning how to, and working on turning my static web apps into an api application. Just something that I can save data with to use between devices, and share with friends. Since I've started this project I've had a ton of ideas on how to make the "ultimate" time tracker/planner type of app. I don't want to abandon the project, but I also don't want to spend the next year building out an app that I will probably abandon in the future.

What do you think? Has there been a time where you have had to stop yourself from building out a passion project?

[0] https://tooldobox.com/