[ohxh]

Just my thought -- perfection is the enemy of good. I've fallen into this before, trying to write the "ultimate" version of some program. Do you use your own web apps today? If you enjoy the work, why not start by focusing product that you need today? If something is good enough to work for you, others will find value too.

[LegoZombieKing]

I think that's what I'm starting to fall into now. I've finished the workable versions of them, and now I'm starting to scope out features that might make them too complex. I use most of these programs every day, and the challenge I'm striking is whether or not I need to create the ultimate, or if I should just stop where I am at.

[sokoloff]

I cycle back and forth between “what would the magnum opus in this space?” and “how little can I get away with here?”

After doing some fantasizing about the former, it helps me to switch frames and build the fastest, shittiest version of it. I have a TODO.txt file with what might come later, but I also have something working that I can learn from and/or get utility from. (For me, the alternative is constant anxiety about “what else could I brainstorm here?” (which is fun) and little in the “what did I accomplish?” (which is rewarding in a different way, but isn’t strictly as ‘fun’).

[bruce511]

Is your goal to have fun building it? Or is your goal to ship it?

I know plenty of projects that will never ship because the author can think of new things faster than he can code. Coding is fun. Shipping, selling and supporting is work. Hence the (subconscious?) goal of never actually shipping.

Which is perfectly OK. But being self-aware enough to know this is happening is both useful and liberating.

Alternatively if your goal is to ship, then ship it already...