Live data from Hacker News

I cancelled Claude: Token issues, declining quality, and poor support

nickyreinert.de

431–440 of 604 posts

Re: I cancelled Claude: Token issues, declining quality, and poor support

#431

Earlier quoted context omitted.

One person is rigorously checking to see if Claude is actually following the spec and one person isn’t?

One is getting paid by a marketing department program and the other isn't. Remember how much has been spent making LLMs and they have now decided that coding is its money maker. I expect any negative comment on LLM coding to be replied to by at least 2 different puppets or bots.

Then you should expect any positive comment to be replied negatively by a competition's puppet or bot too

Re: I cancelled Claude: Token issues, declining quality, and poor support

#433

Earlier quoted context omitted.

One person is rigorously checking to see if Claude is actually following the spec and one person isn’t?

... or one person has a very strong mental model of what he expects to do, but the LLM has other ideas. FWIW I'm very happy with CC and Opus, but I don't treat it as a subordinate but as a peer; I leave it enough room to express what it thinks is best and guide later as needed. This may not work for all cases.

If you don’t have a very strong mental model for what you are working on Claude can very easily guide in you into building the wrong thing.

For example I’m working on a huge data migration right now. The data has to be migrated correctly. If there are any issues I want to fail fast and loud.

Claude hates that philosophy. No matter how many different ways I add my reasons and instructions to stop it to the context, it will constantly push me towards removing crashes and replacing them with “graceful error handling”.

If I didn’t have a strong idea about what I wanted, I would have let it talk me into building the wrong thing.

Claude has no taste and its opinions are mostly those of the most prolific bloggers. Treating Claude like a peer is a terrible idea unless you are very inexperienced. And even then I don’t know if that’s a good idea.

Re: I cancelled Claude: Token issues, declining quality, and poor support

#434

Earlier quoted context omitted.

The number of devs I've worked with who can't touch-type and don't use or know their way around a proper IDE is depressingly large.

Same with debuggers. I run into people with 10 years of experience who are still trying to printf debug complex problems that would be easy with 5 minutes in a debugger. I think we're seeing something similar with AI: There are devs who spend a couple days trying to get AI to magically write all of their code for them and then swear it off forever, thinking they're the only people who see the reality of AI and everyo…

At the same time - there are devs that spend two days setting up a debugger for a simple problem that would be easy with five minutes and printf. AI is a tool and it's a useful tool - it's not always the best tool for the job and the real skill is in knowing when you use it and when not to.

It's a sort of context of life that the easy problems are solved - those where an extreme answer is always correct are things we no longer even consider problems... most of the options that remain have their advantages and disadvantages so the true answer is somewhere in the middle.

Re: I cancelled Claude: Token issues, declining quality, and poor support

#435
First ever time I used ai to code was a week ago, went with the Claude pro because I didn't want to commit.

The 20$ plan has incredible value but also, the limit are just way too tight.

I'm glad Claude made me discover the strength of ai, but now it's time to poke around and see what is more customer friendly. I found deepseek V4 to be extremely cheap and also just as good.

Plus I get the benefit to use it in vs code instead of using Claude proprietary app.

I think that when people goes over the hype and social pressure, anthropic will lose quite a lot of customer.

Re: I cancelled Claude: Token issues, declining quality, and poor support

#436

Earlier quoted context omitted.

They changed it do all of the changes in a virtual cloud environment, then dump the final result at the end of the response. Before it would stream changes, so if it made a minimal fix, then decided to go off on a tangent you could stop it quickly. Now you have to wait 5+ minutes to get a single line of code out of it just to find out it also refactored everything and burned a stack of tokens. No amount of prompting…

> They changed it do all of the changes in a virtual cloud environment, then dump the final result at the end of the response. That’s a hallucination. All they did was hide thinking by default. Quick Google search should easily teach you how to turn it back on (I literally have it enabled in my harness).

Is anything that might be wrong or misinformation now a “hallucination”?

Re: I cancelled Claude: Token issues, declining quality, and poor support

#437
post #47

I feel like I'm using Claude Opus pretty effectively and I'm honestly not running up against limits in my mid-tier subscriptions. My workflow is more "copilot" than "autopilot", in that I craft prompts for contained tasks and review nearly everything, so it's pretty light compared to people doing vibe coding. The market-leading technology is pretty close to "good enough" for how I'm using it. I look forward to the da…

Honestly, it sounds like, assuming you have no ethical qualms, you could get by with a Mac or AMD 395+ and the newest models, specifically QWEN3.5-Coder-Next. It does exactly as you describe. It maxes out around 85k context, which if you do a good job providing guard rails, etc, is the length of a small-medium project. It does seem like the sweet spot between WallE and the destroyed earth in WallE.

Seems like AMD 395+ is only about 16 tokens/s which is 25-33% the speed of SOTA models. Break even on a $3000 machine is ~15 months

Re: I cancelled Claude: Token issues, declining quality, and poor support

#438

Earlier quoted context omitted.

I feel like they are making it harder to use it this way. Encouraging autonomous is one thing, but it really feels more like they are handicapping engaged use. I suspect it reflects their own development practices and needs.

This is something I've thought of as well. The way the caps are implemented, it really disincentivizes engaged use. The 5-hour window especially is very awkward and disruptive. The net result is that I have to somewhat plan my day around when the 5-hour window will affect it. That by itself is a powerful disincentive from using Claude. It has also caused me to use different tools for things I previously would have us…

Wow, weird to see someone mirror my experience so closely. At the $100 plan my day was being warped around how to maximise multple 5 hour sessions so that it felt worth it. Dropped down to the $20 plan and stopped playing the game as I know I'll just consume the weekly usage in the few days I have free. Meanwhile codex gave me a free month, their 5HourUsageWindow:WeeklyUsageWindow ratio feels way better balanced and it gets may more work done from it. Similar to you, any task involving reading/reviewing docs [or code reviews] now insta-nukes claude's usage. My record is 12 minutes so far...

Re: I cancelled Claude: Token issues, declining quality, and poor support

#439

Earlier quoted context omitted.

> You're assuming that finding the places where AI needs help isn't already a larger task than just writing it yourself. Not assuming anything, I'm well versed in how to do this. Anyone who defers to having AI write massive blocks of code they don't understand is going to run into this. You have to understand what you want and guide the AI to write it. The AI types faster than me. I can have the idea and understand a…

The number of devs I've worked with who can't touch-type and don't use or know their way around a proper IDE is depressingly large.

This isn't about touch typing or IDE tricks. I'm an IDE power user and - reasoning aside - I used to run circles around my peers when it comes to raw code editing efficiency. This is increasingly an obsolete workflow. LLMs can execute codebase-wide refactors in seconds. You can use them as a (foot-)shotgun, or as a surgical tool.

Re: I cancelled Claude: Token issues, declining quality, and poor support

#440
I still haven’t seen any other models be as complete as Claude inside Claude Code. I bet Anthropic knows this and they turn the knobs and see people’s reactions… I have been planning with Qwen3.6 Max inside opencode, absolutely game changer. Opus can then follow the plan quite detailed and like this I can make progress on my toy apps on Pro plan at 20/mo.

For work, unlimited usage via Bedrock.

Yes I’d like to get more usage out of my personal sub, but at 20/mo no complains

Post reply on HN