Its so silly everyone being dependent on a black box like this
We are surrounded by black boxes we depend on - have been for at least a century.
Issue: Claude Code is unusable for complex engineering tasks with Feb updates
71–80 of 829 posts
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#72[flagged]
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#73I wish Codex were better because I’d much prefer to use their infrastructure.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#74In my opinion cramming invisible subagents are entirely wrong, models suffer information collapse as they will all tend to agree with each other and then produce complete garbage. Good for Anthropic though as that's metered token usage. Instead, orchestrate all agents visibly together, even when there is hierarchy. Messages should be auditable and topography can be carefully refined and tuned for the task at hand. Ot…
Isn't Claude Code supposed to be like a person? What would the Unix equivalent of that be?
You can't define a product to be "like a person", there is more variance there than any rational product.
I'm purely arguing on technical basis, "person" may fall into either of those camps of philosophy.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#75Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#76I wonder how much of this is simply needing to adapt one's workflows to models as they evolve and how much of this is actual degradation of the model, whether it's due to a version change or it's at the inference level. Also, everyone has a different workflow. I can't say that I've noticed a meaningful change in Claude Code quality in a project I've been working on for a while now. It's an LLM in the end, and even wi…
I've noticed a strong degradation as its started doing more skill like things and writing more one off python scripts rather than using tools. the agent has a set of scripts that are well tested, but instead it chooses to write a new bespoke script everytime it needs to do something, and as a result writes both the same bugs over and over again, and also unique new bugs every time as well.
I'm going absolutely insane with this. Nearly all of my "agent engineering" effort is now figuring out how to keep Opus from YOLO'ing is own implementation of everything.
I've lost track of the number of times it's started a task by building it's own tools, I remind it that it has a tool for doing that exact task, then it proceeds to build it's own tools anyways.
This wasn't happening 2 months ago.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#77I've noticed this as well. I had some time off in late January/early February. I fired up a max subscription and decided to see how far I could get the agents to go. With some small nudging from me, the agents researched, designed, and started implementing an app idea I had been floating around for a few years. I had intentionally not given them much to work with, but simply guided them on the problem space and my co…
There is a huge difference between greenfield development and working with an existing codebase.
I'm not trying to discredit your experience and maybe it really is something wrong with the model.
But in my experience those first few prompts / features always feel insanely magical, like you're working with a 10x genius engineer.
Then you start trying to build on the project, refactor things, deploy, productize, etc. and the effectiveness drops off a cliff.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#78I am curious - is there any hard data (e.g. a benchmark score drop)?
I feel that we look for patterns to the point of being superstitious. (ML would call it overfitting.)
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#79None of this is surprising given what happened last late summer with rate limits on Claude Max subscriptions. And less so if you read [1] or similar assessments. I, too, believe that every token is subsidized heavily. From whatever angle you look at it. Thusly quality/token/whatever rug pulls are inevitable, eventually. This is just another one. [1] https://www.wheresyoured.at/subprimeai/
Ah, and yes, this for real.
Just now I had a bug where a 90 degree image rotation in a crate I wrote was implemented wrong.
I told Claude to find & fix and it found the broken function but then went on to fix all of its call sites (inserting two atomic operations there, i.e. the opposite of DRY). Instead of fixing the root cause, the wrong function.
And yes, that would not have happened a few months ago.
This was on Opus 4.6 with effort high on a pretty fresh context. Go figure.
Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates
#80That analysis is pretty brutal. It's very disconcerting that they can sell access to a high quality model then just stealthily degrade it over time, effectively pulling the rug from under their customers.
If you think that’s brutal, wait until you hear about how fiat currency works