Exactly. Unless you do it to earn money who gives a damn if you have a hundred draft projects? Who except yourself that is. Never finishing anything sucks, as

Exactly. Unless you do it to earn money who gives a damn if you have a hundred draft projects? Who except yourself that is. Never finishing anything sucks, as it gives you the feeling that you.. well.. can't finish anything. My tip is to embrace the fact that a big part of what we start does not need to be finished. I sometimes code a way just for the joy of doing it, that is okay. Not only is it okay, it is also necessary to try out things and play around. Playing is a very good way to learn. And if you give yourself that slack for some projects it is easier to go all strick and I need this done on others. Other than that you need to ask yourself what blocks you from finishing things. E.g. a wise old audio mixing engineer once told me: a mix is never finished, you can always go back and optimize things, forever. Ultimately you need to say it is finished for it to be finished. Software can be similar. Many junior programmers will adjust the scope of their software as they build it and wonder that it never goes anywhere. my tip is to select a problem you profit from being solved. Make a realistic scope what the goal is and do it, so you can go back to your fun project. Boom you just got a thing done.