The taboo of not finishing.

(As I prefaced to many posts I made, don't take this too seriously)

It is very normal in the programming world to get recommended to finish projects.

But I was wondering "what if you don't?".
Of course, we can agree that having little patience or persistence is not good for any endeavor.

But what if this recurrent focus on finishing is also bad?

Granted, I have started dozens of things and only finished one or two of them and none have become popular.
So there's not a lot of support to back my take.

But I definitely learned a lot from these projects. And I definitely had a lot of fun at some points.

In fact, I think if I had switched more often early on I would have been less miserable, and maybe I would have learned more by the virtue of not getting stuck with some project.

Of course this applies as long as you stay within the same field; it doesn't help learning gardening one day but karate the following.

But even then, there are so many hobbies in life that the chance of finding the one that you love and are the best at are very slim. So switching out of the least pleasant ones might bring you to a favorite one.

But, let's go back to programming.

Here, people recommend finishing things as means to become profitable. If you want to live as a gamedev, then you need to sell games, and to do that, you need to finish games.

That is understandable.

But if gamedev isn't your main profit, why is finishing games a requirement?

What's the point of publishing a game that you know looks like shit?

Why? Why should you put time and energy, pain and stress, all the way through the end only to finish or even publish a game that you can feel ashamed of how awful it looks? (because most 1st games look awful).

Why would you ever want to finish something that looks horrible?

First tries are always terrible, and that's fine, nothing wrong with that.

What's wrong is this sheepthought that you should publish to the public every turd that you can produce in your early learning stages.

I've been a programmer for almost 8 years now. I'm not the best out there, but I consider myself ok.

And considering I had some pretty deep depression pits thanks to this mentality, here's my advice to folk having stress with unfinished projects: don't give a single fuck.

If a side project has become stressful, shelf that shit, maybe tell someone about your issues with it. But don't care much about it.

In fact, if you manage to finish a project but it has costed you a great deal of stress, maybe that should be the shameful thing.

Life is too short to waste it considering suicide because you're not a prolific programmer.

And i would argue that iterating 100 times on different things is far more productive (and fun) than fetting stuck or spending shitloads of time on the first one, even if you don't finish any of them.