> Many of us, deep down, are driven more by the joy of making things, solving problems, and seeing people use what we built than by the act of coding itself. After all, many of us decided we wanted to be developers before learning to code, just to create video games or websites. The desire came before the code.

This is a big disconnect that I think has been at the root of many different reactions to LLMs lately. Here on HN I see a lot of "I hate what LLMs did to programming" and equally a lot of "LLMs are awesome, I've never had a better time". I think the disconnect is between people who build software for the end result (having users, the joy of completing a thing, etc) versus building it for the process itself (architecting, coding, debugging).

I'm mainly the kind who enjoys the process. I think of an awesome startup job I had that solved real problems for real customers including some really big firms, but I can't honestly say I ever cared about those problems or the customers. I loved the job because it was technically challenging with a lot of freedom, and the customers were great because they were a source of new interesting details to solve, as well as confirmations that the previous solutions worked.

As such LLMs make me sad because they effectively replace a lot of what I like doing. Doing a refactor to support a new feature, digging through the code to try and understand a bug. One of my strengths as a developer, I think, is that I am fast at familiarizing myself with unfamiliar codebases. That's also a somewhat redundant skill as Claude can answer "how does feature X work in this code" in a small fraction of the time it'd take me.

A few years ago (before the LLM craze) I moved to game dev as my main job, which makes a lot of this easier because I actually care about the end product and the customers (players), so that's a whole new layer of satisfaction in addition to the usual technical one.

Which isn't to say that it's all bad. I've used Claude to get a few things done where I mainly care about the final result and not the process. There was one such project I wanted to get done, I'd had the idea and the data for five or six years, but I found that the implementation would be time consuming, often manual work and much of it involving the kind of tech I don't really enjoy. So I never worked on that but last month, I did the whole thing in a few days with Claude and got exactly the result I wanted.