Ask HN: How to rediscover the joy of programming?

>Here is small excerpt.

...that has nothing to do with the problem in my opinion.

Yes, programming is fun in general but then you come in touch with the reality of the job only to find out once again that

1. you are not making things, most of the time you maintain some old crap because nobody wants to spend time and money on building a new better version etc

2. The thing you are working on is useful but you can't really tell how. The damn thing is so big that all your input after years of work is almost invisible to anyone, even on your team

3. Library here, framework there and most of your own code is just a clever way of putting them together. Fascinating at the beginning, a boring routine a few years later

4. okay, sure, that's enjoyable, sometimes too much.

5. Again - works in theory, breaks after the next meeting. "No time to rework and polish. It works somehow and generates money, so go help those guys finish their work. Bad architecture? Hard to maintain? No matter, management sees only frontend anyway"

You assume "burnout", which s/he didn't specifically state.

S/He asked "Have you rediscovered the joy of programming". Doesn't mean necessarily less programming - might mean more programming of the type s/he got joy out of.

+1

I'm sorry but you are reducing a career to a mere interest.

Changing hobbies is not the same as trying to change what you did for a living for the past decade.

For myself the word that summarizes the best advice here so far is "introspection." A lot of people have mentioned burnout, work/play balance, languages, complexity of modern frameworks, and more. I think it's all constructive, but needs to be interpreted in a personal context.

When I was a kid programming promised to allow me to make incredible things. It was harder than it looked. I mostly abandoned it as a teenager, and then took it up again in college for the same reason. I've been doing it professionally ever since, for over 15 years.

Personally, the joy of any given task is mostly commensurate with how much effort and frustration is directed at the goal, rather than the technology that is supposed to help me get there. This is a big problem with software, because the medium is so complex, but it applies more generally. If I'm making something in the wood shop, it's one thing to be frustrated because I split the end of a board. It's much more deflating to find out that the power saw is broken.

It's partly practical: if I'm in a wood shop, I have the means to deal with a split board. I often do not have the means or the knowledge to fix the power saw. But just as importantly, it's about my own attitude. What would my 12 year old self do? My only choice was to grab the rusty hand saw, make a wobbly cut, and get on with it. Now that I'm older (I can drive and I have money) I'm more at risk of stopping everything to fix the power tools in the name of quality.

I'm currently working on contract and it has felt like an uphill battle. On reflection, I see that only a small fraction of my time is spent making the software that I was hired to build. The rest goes into fighting with the stack and the business side of the job.

The hobby project that I have on the back burner is a single page of javascript (which I am learning) with a horrendous 500 line function that draws stuff. It pays no regard to web development best practices. These are intentional constraints that limit what the output can be for the sake of my enjoyment. It's a ragged, broken mess, but it holds my interest. If I can just get it working, my friends will appreciate it! That for me is the childlike spirit.