That's interesting. I have been thinking about how the vastly different reactions people seem to have to agentic coding could be influenced by what they value about coding. To me it seems like there are three joys in coding:

1. Creating something

2. Solving puzzles

3. Learning new things

If you are primarily motivated by seeing a finished product of some sort, then I think agentic coding is transcendent. You can get an output so much quicker.

If your enjoyment comes from solving hard puzzles, digging into algorithms, how hardware works, weird machine quirks, language internals etc... then you're going to lose nearly all of that fun.

And learning new things is somewhere in the middle. I do think that you can use agentic coding to learn new technologies. I have found llms to be a phenomenal tool for teaching me things, exploring new concepts, and showing me where to go to read more from human authors. But I have to concede that the best way to learn is by doing so you will probably lose out on some depth and stickiness if you're not the one implementing something in a new technology.

Of course most people find joy in some mix of all three. And exactly what they're looking for might change from project to project. I'm curious if you were leaning more towards 2 and 3 in your recent project and that's why you were so unsatisfied with Claude Code.

The creator of OpenClaw had a great line about this:

"If your identity is tied to you being an iOS developer, you are going to have a rough time. But if your identity is 'I'm a builder!' it is a very exciting time to be alive."

Plus, there is no rule that says you can't keep coding if it's faster for you and/or it's quicker in general. e.g I can write a Perl one liner much faster than Claude can. Heck, even if it's not faster and you enjoy coding, just keep coding.

I'm a few years younger than the OP, but I remember the early Internet days. I started with Perl CGI scripts, ASP, even some early server side JS, in the form of Netscape Livewire.

Over the past couple months, I've created several applications with Claude Code. Personal projects that would've taken me weeks, months, or possibly forever, since I generally get distracted and move on to something else. I write pretty decent specs, break things into phases, and make sure each phase is solid before moving on to the next.

I have Claude build things in frameworks I would've never tried myself, just because it can. I do actually look at the code. Some of it is slop. In a few cases, it looks like it works, but it'll be a totally naive or insecure implementation. If I really don't like how it did something, I'll revert and give it another attempt. I also have other AIs review it and make suggestions.

It's fun, but I ultimately gain little intellectual satisfaction from it. It's not like the old days at all. I don't feel like I'm growing my skill set. Yes, I learned "something", but it's more about the capabilities of AI, not the end result.

Still, I'm convinced this is the future. Experienced developers are in the best position to work with AI. We also may not have a choice.

For fun and education purposes, learning and satisfaction are understandable.

For work, companies won't support it. Get it done. Fast. That's the new norm.

When it comes to writing code, I can almost tell before writing code that whether this particular piece of code will be intellectually stimulating to me. If so, I write it myself without thinking about whether Claude might have done it faster. If not, I let Claude write it. Currently I'd estimate maybe 70% of the code falls in the first category, and the remaining 30% is something I would've used a lot of my own willpower to get started anyways.

Also, when I write code myself, I still ask Claude to review it. It's faster than asking a human colleague to review it, so you can have Claude review often. Just today after a five-minute review Claude said a piece of code I wrote had four bugs, three of which were hallucinations and one was a real bug. I honestly do think it would have taken me a bit more than five minutes to find that one real bug.

This past week I found and fixed a bug that happens once in 40,000 transactions working with Claude Code - Opus 4.6. Our legacy app was designed around 2008 and has had zillions of band aids added since then. Nobody (~700 person company) has been able to reliably reproduce this issue to confidently claim that they know what the cause is and how to definitively fix it. That all changed yesterday. I spent today writing up summaries that were shared far and wide. My wizard status is yet again renewed.

I think it depends what you're building. I find it fun, once in a while, an engineer to "not go shoeless" and get some of things I need done.

You're paid by a company to create software, so they can use it to drive business value and make a profit. You did so effortlessly. But it didn't make you feel personally fulfilled. So you're going to go back and re-do it, so you feel better?

How do you think your company's CEO is going to feel when you tell them you could be finishing the software much faster, but you'd rather not, because it feels better to do it by hand?

Your choices are not limited to one extreme or the other.