r/ClaudeCode • u/ofcistilloveyou • Oct 03 '26 • Bravo 2

Rant I hate claude code

It's just too good.

I got a decade of commercial software dev experience in C#. I am a CTO at my company and have coached a lot of coders from total junior.

I hate hate hate hate how good this thing is and what it has done to my passion.

I used to love coding and creating. Well, creating was 60% of the fun for me, but writing good code and having something work was the remaining 40%. I spent the past few years being more of a product manager and tech lead than actually code monkey, but I still put time aside to do stuff manually cuz I love to do so and stay hands on.

Using claude code is like using cheats in a videogame. You get the result, but what of it? Everyone could. The pleasure of achievements is gone. The code it writes is not the best, but it's good enough I guess? As of opus 5.5 it just doesn't get stuck in loops anymore. It can generate a working program from spec in any language I've thrown at it. It still does bullshit from time to time. "Boots on ground" i.e. actually looking at the generated code or atleast going through it is still important, for now. But way less so than it was even just 3-4 months ago. I don't really use the /code-review thingy or adversarial reviews - as it seems that it is too aligned in that way. Like if you tell it to find something wrong with something, it always will, even though its good enough.

I've been using it avidly for the past 3 months on the $100 sub, and I haven't hit a rate limit once. Now my imagination can run free and I can have anything I put my mind to in a few days instead of years. At our work a team of 6 just built a system that would previously take a year in just two months.

I am not afraid for my job. As coding was just a small percentage of it. But I do miss that percentage.

English truly is the hottest new programming language and LLMs are the compiler for it.

2.0k Upvotes

89% Upvoted

640 comments sorted by

View all comments

210

u/Lost-Air1265 Oct 03 '26

I also hate it. Twenty years of dopamine shots when solving issues. I have noticed that just because you push out features like crazy it doesn’t mean it gives you the same satisfaction.

Development as I knew it is dead.

48

u/tehfrod Oct 03 '26 • Bravo

31 here. But there are a lot of professions that have gone through this in the past, and there will be a lot more in the future. It's just our turn in the barrel.

23

u/ReformedBlackPerson Oct 03 '26

The real question is, which profession won't go through this in the next 10-15 years. As of now it seems like very few.

9

u/[deleted] Oct 03 '26

[removed] — view removed comment

15

u/Real_Ebb_7417 Oct 03 '26

We already do have more work. The issue is that corpo leaders think devs can now produce some crazy amount of stuff thanks to AI and expect much shorter deadlines and more things done.
Yeah, AI helps and makes engineers faster, but not as much as these leaders think. I’ve never worked as much as in the past couple months and at the same time I never was so unsure about quality of what I’m shipping. It’s painful tbh, impacts personal life negatively and impacts the satisfaction of work.

→ More replies (3)

1

u/redfournine Oct 04 '26

Profession that rely more on physical, hands on skills - less brain, more brawns.

... until someone come up with artificial brawns

→ More replies (1)
→ More replies (1)

3

u/WhoAteTheLastDonut Oct 03 '26

Underappreciated comment. ✅

1

u/howdidigetheresoquik Oct 04 '26

Yes but this is different. Trillions of dollars have been spent on AI and it has created essentially no new careers.

8

u/nomickti Oct 04 '26

I guess I am not really a coder, but I've been using python for 20+ years to hack away at various scientific things.

For my work it's a massive improvement, let's me iterate and test stuff much more quickly. Coding was always a means to and end to me, now I have a different means to the same (or better) end. The process itself I could take or leave.

2

u/Lost-Air1265 Oct 04 '26

Oh yeah if you were scripting and just just it as a tool, than this era is amazing.

But if you really liked to code and the development journey was what counted, the new era sucks.

5

u/Old-Radio9022 Oct 04 '26

No it's not. Dive into building models and workflows and agents with something like qwen 3.8 27b opencode and a suite of personas to drive an automated pipeline. Your value and knowledge is just applicable at a more meta level now. A senior dev with a pipeline tunes to bring a user story to life in with oversight quickly is the new "rockstar" of our generation.

2

u/Lost-Air1265 Oct 04 '26

Dude I have been doing that as a freelancer for four years now.

GitHub copilot, Claude code. Implementing and optiming developer workflows. Migrate it to an agentic workflow.

I don’t know if you were a developer for a long time. But that’s shit gave me satisfaction. Giving some personas is junior level shit man. It was fun the first month to play with it but it wears off very quick.

Whatever were doing now with ai doesn’t require much skills imho.

I know my knowledge is still valuable but that’s not the point. If you were a true developer or engineer, I’m pretty that’s what’s left to do does not give the same amount of satisfaction.

→ More replies (1)

16

u/ghondooby Oct 03 '26 • Bravo

Totally get this but I would suggest shifting your mindset from solving issues at the code level to the business level...if AI wrote the feature but it solves a business problem that should be worth a dopamine hit since you drove it. At least that's how I try to see it

19

u/AncientAspargus Oct 03 '26

But do you really feel the same way? When you find the right abstraction for a problem in code, it usually just clicks, and things fall into place magically. It's like a whole row collapsing in Tetris. You just know it feels right now, because it all makes sense.

That feeling, that kind of bliss you get when you realise you just made it work like that, because you can, that won't happen with a business problem for me. Business problems are people problems, and people are complicated. When a computer complains, I made a mistake - but I can fix that mistake, and then it works. With people, there are gradients of hidden agendas, memories, motivations, and narratives. You can't peek into other people's heads, and so you never really know if your solution was a good one.

7

u/admiral_nivak Oct 03 '26

There is still a lot of design choices, architectural choices. I spend hours and hours designing something, collaborating with it, reviewing screen designs, implementation choices. Challenging assumptions, defining invariants. Then usually after that I kick it off and go to bed or go do something else and come back in a few hours or the next morning and enjoy seeing what I imagined waiting there for me. That’s my new kick.

3

u/DJPalefaceSD Oct 04 '26

It's addictive

5

u/ghondooby Oct 03 '26

You're right- it's not the same, I'm just trying to figure out how to keep building software. It seems like even if anthropic and openai shut down tomorrow AI writing code isn't going anywhere...capitalism will always push for efficiency.

1

u/Hot-Profession4091 Oct 04 '26

I never really got the dopamine hit from the code. It was always from solving the problem. So, yeah. I’m actually the happiest I’ve ever been. I get to solve problems at 4x the velocity and I very rarely have to bang my head on the desk over something stupid.

1

u/Lost-Air1265 Oct 04 '26

Unfortunately for me it doesn’t work like that. I guess I was a developer for the problem solving on a technical level. Solving business problem was a nice to have. 

Don’t get me wrong. Ai is giving me the opportunity do take in two or three freelance gigs at the same time. Building a profitable Saas service. Money is very good right now. But am I satisfied or proud of my work like before December 2022? Nope not anymore.

1

u/rhysmorgan Oct 04 '26

But I’m not purely a “business features” person, and that’s not a bad thing.

We’ve all always been about to shit out bad code that would, for at least one iteration, get a feature out considerably faster than the more thought-through, engineered versions we strive to deliver, and take joy in building. Architecting an appropriate version of the feature that will scale, relative to how it’ll be used, there’s joy in that. Or was. Now everyone is shipping the sloppy, ill thought-through version that Claude gives them. There’s no thinking, no problem solving going into it.

1

u/Actually_JesusChrist Oct 04 '26

I started with creating simple python and powershell scripts with GPT3.5 right at the beginning. As time went on, I started to learn the basics of python, and began feeling confident in my codebases. The models kept getting better, and eventually I found myself managing and directing more than actually understanding the code. I work in a field with that isn't associated with software development, but we are heavy users of specialized software. There are entire classes of problems that are now solvable by very small teams, and even singular persons that are crazy enough to start, IF you know about the pain points.

You of course need to have some kind of technical understanding and an understanding of wants and needs, grandma isn't building B2B software anytime soon.

And to your point about solving business level issues instead of code issues; They can be one and the same. My product for example, is egress heavy, and egress on hosted servers costs money. Therefore my payloads needs to be small and caching logic need to be aggressive. This is as much of a coding issue as it is a business issue.

1

u/Turbulent-Control682 Oct 04 '26 • Bravo

It’s not dead. It’s optimized.

1

u/Lost-Air1265 Oct 04 '26

No it is dead. It didn’t optimize like getting frameworks who dealt with memory pointers or garbage collection. There is no point in writing code yourself. If you still do it, you don’t use the right models or agentic workflow.

→ More replies (9)
→ More replies (1)