I've learned a ton from all my half-completed projects over the years that has factored directly into my skills at work. I know this sort of sounds... simplist

I've learned a ton from all my half-completed projects over the years that has factored directly into my skills at work. I know this sort of sounds... simplistic... but, well, observe that when you aren't thinking about it, the half-finished projects don't hurt you. You just need to extend that to when you are thinking about them. Your projects are not obligations. Nobody is waiting for them. Nobody is going to fire you, or ground you, or anything else, if you don't finish them. Even if you did put up a post somewhere or something talking about how you've got this wonderful new thing you totes promise will be available in three months... nobody cares yet. And even if they do, well, declare bankruptcy and move on. If that's their biggest disappointment this week they will be in an enviable position. In fact from a perfectly rational point of view, many of those projects maximize their value to you in precisely the state they are in now. It's quite easy for a released project to go quite negative in value to you, due to obligations suddenly actually appearing, having a system that can be hacked and maybe people who can be hurt by a hacked system, etc. I developed a rule of thumb from this. It's very klunky, I won't deny that, I never found a good phrasing for it, but I think of "Never engage in an endeavor where the worst case scenario is complete success." It's really my side projects I'm thinking of when I say this. Do I have an interesting idea for how to create a new type of community site or bulletin board or Reddit competitor? Sure, that's fun to program, but what if it actually worked? Do I want to actually own such a thing? Goodness gracious no. So maybe I do the fun part and then just let it sit on the hard drive, and call it a win.