Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

nickyreinert.de

Post reply on HN
Print view View original

401–410 of 604 posts

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

#401

Post by hirvi74 »

prmph wrote: post #370
onlyrealcuzzo wrote: post #294

Earlier quoted context omitted.

> Or just don't use AI to write code. Anecdata, but I'm still finding CC to be absolutely outstanding at writing code. It's regularly writing systems-level code that would take me months to write by hand in hours, with minimal babysitting, basically no "specs" - just giving it coherent sane direction: like to make sure it tests things in several different ways, for several different cases, including performance, comp…

But, how do you know the code is good? If you do spot checks, that is woefully inadequate. I have lost count of the number of times when, poring over code a SOTA LLM has produced, I notice a lot of subtle but major issues (and many glaring ones as well), issues a cursory look is unlikely to pick up on. And if you are spending more time going over the code, how is that a massive speed improvement like you make it seem…

> But, how do you know the code is good?

Honestly, this more of a question about scope of the application and the potential threat vectors.

If the GP is creating software that will never leave their machine(s) and is for personal usage only, I'd argue the code quality likely doesn't matter. If it's some enterprise production software that hundreds to millions of users depend on, software that manages sensitive data, etc., then I would argue code quality should asymptotically approach perfection.

However, I have many moons of programming under my belt. I would honestly say that I am not sure what good code even is. Good to who? Good for what? Good how?

I truly believe that most competent developers (however one defines competent) would be utterly appalled at the quality of the human-written code on some of the services they frequently use.

I apply the Herbie Hancock philosophy when defining good code. When once asked what is Jazz music, Herbie responded with, "I can't describe it in words, but I know it when I hear it."

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

#402

Post by spaceman_2020 »

taytus wrote: post #102
rectang wrote: 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…

I'd recommend Kimi k2.6 for your use. It is an excellent model at a fraction of the cost, and you can use Claude Code with it. I did a 1:1 map of all my Claude Code skills, and it feels like I never left Opus. Super happy with the results.

did you just copy-paste or is there a difference in the way kimi uses skills?

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

#403

Post by wg0 »

jonas21 wrote: post #363
wg0 wrote: post #262

Earlier quoted context omitted.

> Writing detailed specs and then giving them to an AI is not the optimal way to work with AI. It is NOT the way to work with humans basically because most software engineers I worked with in my career were incredibly smart and were damn good at identifying edge cases and weird scenarios even when they were not told and the domain wasn't theirs to begin with. You didn't need to write lengthy several page long Jira ti…

> That's why every chat box has that "Regenerate" button. Wait, are you doing this in the web chat interface?! That's definitely not a good way. You need to be using a harness (like Claude Code) where the agent can plan its work, explore the codebase, execute code, run tests, etc. With this sort of set up, your prompts can be short (like 1 to 5 sentences) and still get great results.

I use claud CLI or OpenCode. The "Regenerate" example is just to illustrate that same prompt would produce different output each time. You're rolling a dice.

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

#404

Post by 2ndorderthought »

janwillemb wrote: post #19

This is what worries me. People become dependent on these GenAI products that are proprietary, not transparant, and need a subscription. People build on it like it is a solid foundation. But all of a sudden the owner just pulls the foundation from under your building.

Imagine if anthropic and openai went bankrupt in the next 2 years. If you look at their financials its a real possibility.

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

#405

Post by 2ndorderthought »

Someone1234 wrote: post #51
GaryBluto wrote: post #25

Earlier quoted context omitted.

Luckily local AI is becoming more feasible every day.

It feels more and more like OpenAI/Anthoropic aren't the future but Qwen, Kimi, or Deepseek are. You can run them locally, but that isn't really the point, it is about democratization of service providers. You can run any of them on a dozen providers with different trade-offs/offerings OR locally. They won't ever be SOTA due to money, but "last year's SOTA" when it costs 1/4 or less, may be good enough . More quantit…

You can run local models on junker laptops for specific tasks that are about as good as last years SOTA. If the manufactured compute hardware shortage wasn't happening a lot more people would be running two months ago SOTA locally right now. Funny thoughts...

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

#406

Post by sarchertech »

janalsncm wrote: post #379
onlyrealcuzzo wrote: post #294

Earlier quoted context omitted.

> Or just don't use AI to write code. Anecdata, but I'm still finding CC to be absolutely outstanding at writing code. It's regularly writing systems-level code that would take me months to write by hand in hours, with minimal babysitting, basically no "specs" - just giving it coherent sane direction: like to make sure it tests things in several different ways, for several different cases, including performance, comp…

How can a person reconcile this comment with the one at the root of this thread? One person says Claude struggles to even meet the strict requirements of a spec sheet, another says Claude is doing a great job and doesn’t even need specific specs? I have my own anecdata but my comment is more about the dissonance here.

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

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

#407

Post by djyde »

rectang wrote: 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…

[dead]

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

#408

Post by y42 »

joozio wrote: post #270

Funny. I thought I was the only one. Then I found more people and now you wrote about that. Just this week I also wrote about Claude Opus 4.7 and how I came back to Codex after that: https://thoughts.jock.pl/p/opus-4-7-codex-comeback-2026

I like your blog and I can totally relate to this article - it's like something I wanted to write about for a couple of weeks now. :D

https://thoughts.jock.pl/p/adhd-ai-agent-personal-experience...

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

#409

Post by imetatroll »

fourside wrote: post #52
GaryBluto wrote: post #25

Earlier quoted context omitted.

Luckily local AI is becoming more feasible every day.

Maybe for folks who are deep into this, but it’s not exactly accessible. I tried reading up on it a couple of months ago, but parsing through what hardware I needed, the model and how to configure it (model size vs quantization), how I’d get access to the hardware (which for decent results in coding, new hardware runs $4k-$10k last I checked)—it had a non trivial barrier of entry. I was trying to do this over a long…

For me the big hangup is the hardware. If I could find a simple guide to putting together a machine that I can run off an outlet in my home, I am sold. The problem is that I haven't found this yet (though I suppose I haven't looked very hard either).

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

#410

Post by fluidcruft »

p_stuart82 wrote: post #222
Retr0id wrote: post #108

Earlier quoted context omitted.

Another big one for me is that they dropped the cache TTLs. It is normal for me to come back to a session an hour later, but someone "autopilot"-ing won't have such gaps.

not just the cache though. every time you stop and come back, it basically reloads the whole session. if you just let it keep going, it counts like one smooth run. you hit the wall faster for actually checking its work.

It was probably the bug about cache getting purged after 5min rather than 1hour. You can review things pretty well within an hour. 5min is a real crunch. 5min doesn't mix with multitasking or getting interrupted.
Post reply on HN