Earlier quoted context omitted.
I can see how that works: this is like building a dependency, a habit if you wish. I think the tighter you couple your workflow to these tools the more dependent you will become and the greater the let-down if and when they fail. And they will always fail, it just depends on how long you work with them and how complex the stuff is you are doing, sooner or later you will run into the limitations of the tooling. One wa…
Good advice about the dependency. This stuff is definitely addictive. I've been in something of a manic episode ever since I subscribed to this thing. I started getting anxious when I hit limits. I wouldn't say that Claude is failing though. It's just that they're clearly messing with it. The real Opus is great.
Issue: Claude Code is unusable for complex engineering tasks with Feb updates
631–640 of 829 posts
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#632Earlier quoted context omitted.
Stealthily degrade the model or stealthily constrain the model with a tighter harness? These coding tools like Claude Code were created to overcome the shortcomings of last year's models. Models have gotten better but the harnesses have not been rebuilt from scratch to reflect improved planning and tool use inherent to newer models. I do wonder how much all the engineering put into these coding tools may actually in…
I've been using pi.dev since December. The only significant change to the harness in that time which affects my usage is the availability of parallel tool calls. Yet Claude models have become unusable in the past month for many of the reasons observed here. Conclusion: it's not the harness. I tend to agree about the legacy workarounds being actively harmful though. I tried out Zed agent for a while and I was SHOCKED…
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#633Called it 10 days ago: https://news.ycombinator.com/item?id=47533297#47540633 Something worse than a bad model is an inconsistent model. One can't gauge to what extent to trust the output, even for the simplest instructions, hence everything must be reviewed with intensity which is exhausting. I jumped on Max because it was worth it but I guess I'll have to cancel this garbage.
Use it to set up the strictest possible custom linting rules.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#634Its so silly everyone being dependent on a black box like this
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#635Earlier quoted context omitted.
Was there a change in Claude Code system prompt at that time that nudges Claude into simplistic thinking? Here is a gist that tries to patch the system prompt to make Claude behave better https://gist.github.com/roman01la/483d1db15043018096ac3babf5... I haven’t personally tried it yet. I do certainly battle Claude quite a lot with “no I don’t want quick-n-easy wrong solution just because it’s two lines of code, I wan…
Holy sweet LLM, this gist is crazy. Why did they do this to themselves? I am going to try this at home, it might actually fix Claude.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#636Earlier quoted context omitted.
When you submit a /bug we get a way to see the contents of the conversation. We don't see anything else in your codebase.
Was there a change in Claude Code system prompt at that time that nudges Claude into simplistic thinking? Here is a gist that tries to patch the system prompt to make Claude behave better https://gist.github.com/roman01la/483d1db15043018096ac3babf5... I haven’t personally tried it yet. I do certainly battle Claude quite a lot with “no I don’t want quick-n-easy wrong solution just because it’s two lines of code, I wan…
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#637Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#638The assertion in the issue report is that Claude saw a sharp decline in quality over the last few months. However, the report itself was allegedly generated by Claude. Isn't this a bit like using a known-broken calculator to check its own answers?
it's analysis of what is broken is probably wrong or at least incomplete though
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#639Claude could get too much creative and bloat it's way for non-coding tasks, as these tasks cannot be "sandboxed" with full specs as it can be done for coding.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#640Earlier quoted context omitted.
I've noticed this as well. "Now you should stop X and go do Y" is a phrase I see repeated a lot. Claude seems primed to instruct me to stop using it.
as someone who uses deepseek, glm and kimi models exclusively, an llm telling me what to do is just off the wall glm and kimi in particular, they can't stop writing... seriously very eager to please. always finishing with fireworks emoji and saying how pleased it is with the test working. i have to say to write less documentation and simplify their code.
You need to train them on a special "stop token" to get them to act more human. (Whether explicitly in post-training or with system prompt hacks.)
This isn't a general solution to the problem and likely there will never be one.