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

331–340 of 604 posts

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

#331

Post by rglover »

ChicagoDave wrote: post #296

I think there’s a clear split amongst GenAI developers. One group is consistently trying to play whack-a-mole with different models/tools and prompt engineering and has shown a sine-wave of success. The other group, seemingly made up of architects and Domain-Driven Design adherents has had a straight-line of high productivity and generating clean code, regardless of model and tooling. I have consistently advised all…

Dead on. Any company not thinking about this like the 2nd group is setting themselves up for a bad time (and sadly, anecdotally, that seems to be an emerging majority).

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

#332

Post by kazinator »

_puk wrote: post #327
mathisfun123 wrote: post #307

Earlier quoted context omitted.

bro do you really not understand that that's a game played for your sake - it checks boxes yes but you have no idea what effect the checking of the boxes actually has. like do you not realize/understand that anthropic/openai is baking this kind of stuff into models/UI/UX to give the sensation of rigor.

Not to knee jerk on a bro comment, but, bro.. Are you seriously saying that breaking a large complex problem down into it's constituent steps, and then trying to solve each one of them as an individual problem is just a sensation of rigour?

To some extent, I could agree with that idea. One purpose of that process is to match the impedance between the problem, and human cognition. But that presumes problem solving inherently requires human cognition, which is false; that's just the tool that we have for problem solving. When the problem-solving method matches the cognitive strengths and weaknesses of the problem solvers, they do have a certain sensation of having an upper hand over the problem. Part of that comes from the chunking/division allowing the problem solvers to more easily talk about the problem; have conversations and narratives around it. The ability to spin coherent narratives feels like rigor.

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

#333

Post by snarkconjecture »

wg0 wrote: post #262
Aurornis wrote: post #232

Earlier quoted context omitted.

Writing detailed specs and then giving them to an AI is not the optimal way to work with AI. That's vibecoding with an extra documentation step. Also, Sonnet is not the model you'd want to use if you want to minimize cleanup. Use the best available model at the time if you want to attempt this, but even those won't vibecode everything perfectly for you. This is the reality of AI, but at least try to use the right mod…

> 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…

> the underlying working principles are the same as GPT-2

I don't think anyone was claiming otherwise. Sonnet is still better at writing code than GPT-2, and worse than Opus. Workflows that work with Opus won't always work with Sonnet, just as you can't use GPT-2 in place of Sonnet to do code autocomplete.

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

#334

Post by giancarlostoro »

dheera wrote: post #46
giancarlostoro wrote: post #14

I'm torn because I use it in my spare time, so I've missed some of these issues, I don't use it 9 to 5, but I've built some amazing things, when 1 Million tokens dropped, that was peak Claude Code for me, it was also when I suspect their issues started. I've built up some things I've been drafting in my head for ages but never had time for, and I can review the code and refine it until it looks good. I'm debating try…

Claude Code now has an official telegram plugin and cron jobs and can do 80% of the things people used OpenClaw for if you just give it access to tools and run it with --dangerously-skip-permissions.

I don't use OpenClaw is what I'm saying though, I use Claude Code for coding, and would like to better equip Claude by a custom coding harness that has superior tooling out of the box, but that is fair.

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

#335

Post by _puk »

Maxatar wrote: post #257
sidrag22 wrote: post #220

Earlier quoted context omitted.

> fully understand every change and every single line of the code. im probably just not being charitable enough to what you mean, but thats an absurd bar that almost nobody conforms to even if its fully handwritten. nothing would get done if they did. But again, my emphasis is on that im probably just not being charitable to what you mean.

You're most likely being pedantic, like when someone says they understand every single line of this code: x = 0 for i in range(1, 10): x += i print(x) They don't mean they understand silicon substrate of the microprocessor executing microcode or the CMOS sense amplifiers reading the SRAM cells caching the loop variable. They just mean they can more or less follow along with what the code is doing. You don't need to b…

Understand your code in this day and age likely means hit the point of deterministic evaluation.

print(X) is a great example. That's going to print X. Every time.

Agent.print(x) is pretty likely to print X every time. But hey, who knows, maybe it's having an off day.

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

#336

Post by giancarlostoro »

Der_Einzige wrote: post #75
dheera wrote: post #46

Earlier quoted context omitted.

Claude Code now has an official telegram plugin and cron jobs and can do 80% of the things people used OpenClaw for if you just give it access to tools and run it with --dangerously-skip-permissions.

The /loop command which is supposed to be the equivilant to heartbeat.md is EXTREMELY unreliable/shitty.

I use it sparingly with my guardrails project. I basically tell it to:

Check any tasks if it's not currently working on one, and to continue until it finishes, dismiss this reminder if it's done, and then to ensure it runs unit tests / confirms the project builds before moving on to the next one. Compact the context when it will move to the next one. Once its exhausted all remaining tasks close the loop.

Works for me for my side projects, I can leave it running for a bit until it exhausts all remaining tasks.

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

#337

Post by kx_x »

After the fixes in Claude Code, Opus 4.6/4.7 have been performing well.

Before the fixes, they were complete trash and I was ready to cancel this month.

Now, I'm feeling like the AI wars are back -- GPT 5.5 and Opus 4.7 are both really good. I'm no longer feeling like we're using nerfed models (knock on wood)!

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

#338

Post by thepasch »

deckar01 wrote: post #254
couchdb_ouchdb wrote: post #130

Earlier quoted context omitted.

I don't think i'd let it think more than 5 minutes without killing the process.

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).

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

#339

Post by rurban »

That's bad for him, because he already had a cheap plan. Now he wont get it back that easy.

Pro is gone. OpenAI plans are more expensive. He can only buy a Kimi plan, which is at least better than Sonnet. But frontier for cheap is gone. Even copilot business plans are getting very expensive soon, also switching to API usage only.

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

#340

Post by jjwiseman »

buredoranna wrote: post #328
gwerbin wrote: post #225

Earlier quoted context omitted.

Or just don't use AI to write code. Use it as a code reviewer assistant along with your usual test-lint development cycle. Use it to help evaluate 3rd party libraries faster. Use it to research new topics. Use it to help draft RFCs and design documents. Use it as a chat buddy when working on hard problems. I think the AI companies all stink to high heaven and the whole thing being built on copyright infringement stil…

> the whole thing being built on copyright infringement I am not a lawyer, but am generally familiar with two "is it fair use" tests. 1. Is it transformative? I take a picture, I own the copyright. You can't sell it. But if you take a copy, and literally chop it to pieces, reforming it into a collage, you can sell that. 2. Does the alleged infringing work devalue the original? If I have a conversation with ai about "…

And in Bartz v. Anthropic, the court found that Anthropic training their LLMs on books was "highly transformative."
Post reply on HN