Neither.
It's amazing to know you can create things but that doesn't make the process, as of now, to make it, "fun" (based on my view of fun programming should be).

I only program as a hobby. I had intended to make programming my career originally, but towards the end of my degree, the stories I heard from too many career programmers put me off the idea. Being told what to code, and how to code as a job just didn't interest me. I loved programming too much to take a job that would probably make me hate it.

This was a long time ago, before the internet came along and changed everything. If I was that age now, I would try to make it as an independent programmer, but that wasn't really an option in New Zealand 20 years ago.

But I still get to do it in my own time, and I still enjoy it, 30+ years on.

If I was that age now, I would try to make it as an independent programmer, but that wasn't really an option in New Zealand 20 years ago.

Unless you program software for yourself or by your own directions there isn't such a thing as an "independent programmer".

You can work out the exact specifications of your customer's needs, start building a sensible codebase for all of it and then have to rewrite your corefunctions and hack into everything because your customer decides that it would be awesome if the wooden hut had a magetower and a small pizza booth on the west side. One of the most noticable changes in the way software is written now is that it needs to change frequently, with changes decided by people that have absolutely no clue how that program is internally organized.

Both. It can be very enjoyable, exciting, very frustrating, or just tedious.

I agree. So far I've found it a lot of fun but very stressful at times.

Sometimes you hit a wall and just have no idea what to do.

BUT MAN. That feeling when you get it right You feel like a god.

So personally, I have to say fun.

I chosen the last option because it takes so long.

Both. No matter how boring work can sometimes get, I never forget - I write software for a living! Win!

I spent 20 years doing jobs I hated so I could go home and code in the evenings. Now I write code all day, go home and write code in the evenings. This is a perfect situation for me. If it isn't for you, maybe you are more interested in the end result than the process? Not a good precursor to becoming a good programmer in my experience but YMMV of course.

Programming is a hobby for me, so it's fun for me, because as soon as I would get tired of it, I just leave it. Then I come back later when I'm powered up again.

If you're not having fun, do something you enjoy

Its a fun and interesting hobby for me. I enjoy it because I am interested in knowing how games work under the hood and what powers the technology and also want to create my own tech(even if it sucks).

Fun. After 20 years I still enjoy programming and learning languages. The day it is no longer fun I will find something new to do.