> Idk folks, maybe it's because I actually don't like writing software as much as I thought I did. I'm realizing I actually like making products and creatively solving problems, and software is a mildly enjoyable means to and end for that. I also like many aspects of the job of programming (money, sitting on my ass, dictating much of my workday, feeling like a boss, also money, etc). I was lucky to be alive in a time when that role was in demand but I can now see that is coming to an end for at least 80% of us. Yes, probably you, and probably me.

Yep, this is what I realised. I like solving a problem/fixing something. I am not really interested in hooking up a Go/Python/C# web service to a database for the umpteenth time.

I've been partially vibe-coding a new desktop environment for Linux and creating my own UI framework. I know how UI frameworks generally work, and I know how desktop environments generally work. What I want to do is build a DE that works well and fits my vision of how it should work functionally.

I am reasonable at C++ (I don't do it professionally). Do I want to spend 20 hours doing a load of UI boilerplate code in C++? No, I don't. I am sure I can do it, I've written UI frameworks before in other languages. But I get the machine to do all the boring stuff, and I develop the product. If the code it starts churning out is crap, I have the ability to fix it.

There seems to be a lot of crap about not being able to code after using AI for a few months. This is rubbish. I used to code when I was a kid in BBC BASIC and didn't for years, I then started coding again in my early 20s and all of the stuff I learned came back to me, and I was programming in Java. Same recently, I didn't program for about 4 months and had to program without the AI as the AI couldn't solve what I was doing, and I was fine.