Live data from Hacker News

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

nickyreinert.de

451–460 of 604 posts

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

#452

Earlier quoted context omitted.

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

That’s interesting to hear as for me Claude has been quite good about writing code that fails fast and loud and has specifically called it out more than once. It has also called out code that does not fail early in reviews.

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

#453

Earlier quoted context omitted.

This was a real issue, and Anthropic recently awknowledged it: https://www.anthropic.com/engineering/april-23-postmortem Of course, it sucks when companies screw up ... but at the same time, they "paid everyone back" by removing limits for awhile, and (more importantly to me) they were transparent about the whole thing. I have a hard time seeing any other major AI provider being this transparent, so while I'm annoyed…

Amusingly, when a coworker was looking for this postmortem, they found a different postmortem of three Claude issues that caused decay. This one was in the platform, not in Claude Code: https://www.anthropic.com/engineering/a-postmortem-of-three-... I think there's a certain amount of running with scissors going on here. I appreciate the transparency, but the time to remediation here seems pretty long compared to the…

[deleted]

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

#454

Earlier quoted context omitted.

I always wonder if anyone out there thinks they're not making money off of other people's work. If you're coding, writing a fantasy novel, taking a photograph or drawing a picture from first principals you came up with yourself I applaud you though.

You are absolutely right. Seriously though, I do think that is the case. It would be self-righteous to argue otherwise. It's just the scale and the nature of this, that makes it so repulsive. For my taste, copying something without permission, is stealing. I don't care what a judge somewhere thinks of it. Using someone's good will for profit is disgusting. And I hope we all get to profit from it someday, not just a s…

This kind of thinking seems like a road for people to have to pay a license for the rest of their life after going to school for the knowledge they "stole" from their textbooks.

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

#455
post #202

I write detailed specs. Multifile with example code. In markdown. Then hand over to Claude Sonnet. With hard requirements listed, I found out that the generated code missed requirements, had duplicate code or even unnecessary code wrangling data (mapping objects into new objects of narrower types when won't be needed) along with tests that fake and work around to pass. So turns out that I'm not writing code but I'm r…

I use open spec to negotiate requirements before the handoff, it's helped me a lot. You could also use GSD2 or Amazon's Kiro, or Spec Kit but I find they have too many stages and waste tokens.

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

#456

Earlier quoted context omitted.

Sure, Opus is next level than Sonnet, but it still doesn't free OP from these handcuffs - It is reading the code, understanding it and making a mental model that's way more labour intensive.

The OP's problem was treating the situation as two extremes: Either write everything myself, or defer entirely to the AI and be forced to read it later. I was trying to explain that this isn't how successful engineers use AI. There is a way to understand the code and what the AI is doing as you're working with it. Writing a spec, submitting it to the AI (a second-tier model at that) and then being disappointed when i…

Is doing that faster than just writing it by hand? Remember to include the time you need to review the code afterwards. The research so far says it isn't faster. Yet people keep doubling down on it and thinking winning an Internet argument is going to matter when it hits the fan in the near future.

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

#457
post #441

I see a lot of people struggling to work with agents. This post has a good example: > “you can’t be serious — is this how you fix things? just WORKAROUNDS????” If this is how you’re interacting with your agents I think you’re in for a world of disappointment. An important part of working with agents is providing specific feedback. And beyond that making sure this feedback actually available to them in their context w…

After you see it skip reasoning so many times and saying "actually the simplest fix is" the laziest thing ever you get kind of tired of babysitting it.

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

#458
I use Aider nowadays, and will probably cancel my Github multi AI bundle subscription due to the new training policy. I find using Aider with the new open models and using Open Spec to negotiate requirements before the handoff, has helped me a lot.

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

#460

Earlier quoted context omitted.

Might as well just write the code yourself at that point. And as a bonus, end up with a much better understanding of the codebase (and way better code)

> Might as well just write the code yourself at that point "We have this thing that can speed your code writing 10x" "If it isn't 1000x and it doesn't give me a turnkey end to end product might as well write the whole thing myself" People have forgotten balance. Which is funny, because the inability of the AI to just do the whole thing end to end correctly is what stands between 10 developers having a job versus 1 de…

The goalposts move every month. We’re at the stage where handing an entire specification to a mid-tier AI and walking away while it does all the work and then being disappointed that it wasn’t perfect means it’s useless.
Post reply on HN