Yes. There is also reason to believe that the ecosystem is on the path to migrating to one where human developers are an afterthought at best. In the current phase we have lots of more stuff in markdown and other human readable formats and programming languages for sure but there’s little reason to believe that they will stay that way as humans get further from the code in general and the primary consumers and producers are AI. It would be strange if it remains optimized for English-speaking humans for very long.

Open source development has become buried in an avalanche of AI generated code as well so the character of a lot of hobby programming in that domain has changed drastically.

>People are complaining that they don't get to enjoy what they do for work any more.

And that's OK.

I remember reading this New Yorker piece[0] when it came out 8 years ago about how the proliferation of electronic health records software in hospitals was driving older doctors towards retirement, and it made me ponder how many people hated using the software I've built professionally over the course of my career.

Change comes to every profession, and it's never universally helpful or productive. I'm very much in the middle of the road on the AI booster/skeptic continuum, but I know it's not going away.

And getting to "enjoy" the work was always just a perk. Where in labor law in any country throughout history guarantees enjoyment of the work? Surprisingly few people throughout history have been able to say they enjoyed their work. It's always been a trade of time for money, everything else is table stakes. I'm finding new ways to find enjoyment both in the job and out of it, and if that time-for-money trade stops being worth it, I'll figure out something else.

0: https://www.newyorker.com/magazine/2018/11/12/why-doctors-ha...

Given the amount of complaints and generally downtrending tone on HN over the past decade and a half, did people really enjoy programming for work? It feels like the vicissitudes of the market, from the “move fast and break stuff and technical debt be damned” era of ZIRP, to “move even faster because now companies have to show profit and we are post-ZIRP cracked 100x engineers” just led to a lot of sloppy inelegant code, features and products built that never shipped, and unending meetings about half-baked business requirements. And a lot of the programming just ended up writing API glue code.

If you’re a The Art of Computer Programming-reading, code golf-competing, blogging neat elegant hacks kind of programmer, were you really getting that experience coding at work?

It's almost as if this problem was forseeable.