Comment by atoav

I am also used OPs method and it is the reason I now work in a technical job despite having studied art. I just followed my curiosity and that lead to an expert-level understanding in some fields (I later got some formal proof of said expertise).

I don't think that "follow your instinct" is good advice for everyone, but maybe you should understand it more as a "follow your instinct which productive thing you want to do next".

In your examples, writing small programs is the only truly productive thing, the others are consumptive. I learned all I know about programming (I program for a living) from such projects, some of which took weeks of my time. The trick about the instinct thing is that I trust my instincts when I should move to another productive thing that interests me more. So I may be working on a long term programming project, then my instinct tells me when I continue I will start hating it, so I go and work on a hardware project I haven't finished. Before I can switch I need to ensure a state at which I can pick up later on, so I do that before. This way I have a high number of parallel projects each of which is always left in a state where switching between them feels managable.

Of course finishing them is a goal sometimes, but since I am working on many things and always work on the thing that feels good I finish things regularly and have a good time doing it. I also abandon/trash projects, especially if my understanding of a domain has expanded and my initial idea turns out to be misguided. That is okay, I learned something from that which should be your ultimate goal anyways.