The problem with tiddlywiki?

[TW Tones]

Over recent months, 

I have run into a problem with tiddlywiki and want to share it to forewarn you and learn what people do to avoid it.

TiddlyWiki it extremely flexible and refine-able. Its capabilities are infinite, if not almost infinite, and new possibilities arrive every day.

Some would say, "That is not a problem", but for many it is. If you have any tendency to perfectionism it can be a curse. We can always make thing better smarter, faster more intuitive, and yes simpler. Add to that my own desire to create reusable, hack-able solutions that help new and existing users, that is, I focus on developing tiddlywiki as a platform, to prepare it for any possible requirement and the work expands to fill my "vision".

Now I understand and are suspicious of the, "Minimal Viable Product" MVP idea. I do create prototypes to test a possibility, in some ways these are MVP's but I am reluctant to turn it into a "product"  until I have lived with it for a while, and if can't find a better way. Someone or myself usually do find another way. 

Most days someone posts a new innovative solution, method or idea that was not thought of before.

How do you handle this problem?

TW Tones

[PMario]

Hi Tony,

In software development, there is a "rule of thumb". You can finish a project up to 80% in 20% of the time.

If I create utilities for my own use, I usually stop developing, when they work "just good enough" for me. To publish them as a plugin or add them to my library, I need at least 2 more days for additional testing and UX polishing. Most of the time it also needs several iterations once the stuff is published.

IMO the conclusion is: you can finish 1 project 100% in using 100% of the time, OR you can create 5 projects up to 80% also using 100% of the time.

have fun!

mario

[TW Tones]

Ha Ha, Mario,

That rule is similar to the one I have used, It takes 80% of the time to get 80% of the work done, and 80% of the time to get the final 20% done. 

Yes - it adds up to 160%

The problem for me is I seem to discover more or better is possible, so the work to be done expands, before I approach even 80% of the original design idea. 

Truth is I would prefer to be in this situation than others because I know in the long run a great many features will be available. It can just be a little frustrating while "on the journey".

TW Tones

[Saq Imtiaz]

Pretty much what @pmario said.

If I create utilities for my own use, I usually stop developing, when they work "just good enough" for me. To publish them as a plugin or add them to my library, I need at least 2 more days for additional testing and UX polishing. Most of the time it also needs several iterations once the stuff is published. 

+1 

I can often prototype something simple in an hour but polishing it for public consumption might take a day or more. Taking an iterative approach is usually a good idea, but then you need to be able to commit to the future hours of work that it will entail.

 As someone with perfectionist tendencies, this is something I have to work hard to remind myself: sometimes great becomes the enemy of good.

[Birthe C]

You are all giving the reason, we should all be so grateful, that so many are ready to use the extra time to publish their goodies.

@TW Tones,

How do you handle this problem?

Most days someone posts a new innovative solution, method or idea that was not thought of before.

That is just lovely!

Realise that 24 hours each day is what you have got. If you use all of them "playing" with tiddlywiki it will not end up well. Not well for work/business or private life. If that is not enough to overcome the drug like addiction to TW, then think  you will soon be in a condition not able to follow much of the next things to come in this group. We may need to use Eric's Timer for that. You wanted a sound for that, maybe it is a TW lock you need.

I am sure you are not alone with this problem.

Birthe