HNHacker News
TopNewBestAskShowJobs

dacorvo

1 karma · joined September 4, 2026

submissionscomments
dacorvo··on It's still ok to enjoy programming
I've been programming since I was a teenager, starting in the 80s on my Sinclair ZX Spectrum. At the time I never thought I could make a living out of it. After graduating as a generalist engineer, I went to several job interviews and quickly realized that the jobs they had in mind for me would make me unhappy. It was almost by chance that I applied for a software development role, since those were not usually open to generalist engineers (that changed pretty quickly).

The first years were amazing: I was paid to do my hobby. We wrote pretty much everything from scratch, which was fun, but arguably not very productive. Then came middleware and higher-level frameworks and languages. For a few years it was not that fun, since we were tied to very rigid development environments. Then Linux arrived and started the big open source wave, which set us free again: you could build anything on top of amazing libraries, and even contribute to them.

But for me the fun did not last long. A large part of software was now delivered as a service, with fierce competition and little room for craftsmanship. You could still find pockets of freedom at the edges of software engineering, and that's what I did, exploring every emerging field I could. Every single time, as the field matured, development got industrialized and less fun.

Looking back on all my years as a developer, this is the constant: I always found ways to have fun developing, but it never lasted long, which explains why I explored so many different areas (that, and I get bored pretty quickly, to be honest). That said, I was lucky to work in cutting-edge environments where pet projects were allowed.

Now, I have stopped writing code, but I haven't stopped developing. The rise of coding agents took me by surprise, even though I work at an ML company, and it threw me way out of my comfort zone. I quickly realized there was no going back, and that I had to embrace these tools instead of fighting them (incidentally, that's what I'm paid for, so not exactly a bold move). I am not at peace with the whole coding agent experience (far from it), but I am gradually building workflows that are less frustrating, and sometimes I even manage to feel some of the fun I used to have. Instead of writing code, I spend a lot more time in very long design sessions. I don't implement anything myself, but seeing the result work as expected is still rewarding.

The real pain point is reviewing. The agents are much more productive than I ever was, and they produce more code than I can possibly review (more than any team I ever led). I might have figured out a solution: using intermediate languages that are easier to review (perhaps formal languages). And yes, I still review. Otherwise my code rots pretty quickly, twisted by the agents' inherent lack of intent. They will happily solve a problem that would not need solving if the design had followed the intent. I want to believe I can still have fun once I get past the current hurdles. Some days, interacting with an agent feels like calling customer support: it is very polite, completely understands my frustration, and goes right back to the script.