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

Issue: Claude Code is unusable for complex engineering tasks with Feb updates

github.com

Post reply on HN
Print view View original

361–370 of 829 posts

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#361

Post by notatallshaw »

rafaelmn wrote: post #325
raincole wrote: post #227

Earlier quoted context omitted.

> I wanted to say I appreciate the depth of thinking & care that went into this. The irony lol. The whole ticket is just AI-generated. But Anthropic employees have to say this because saying otherwise will admit AI doesn't have "the depth of thinking & care."

Ticket is AI generated but from what I've seen these guys have a harness to capture/analyze CC performance, so effort was made on the user side for sure.

The note at the end of the post indicates the user asked Claude to review their own chat logs. It's impossible to tell if Claude used or built a a performance harness or just wrote those numbers based on vibes.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#362

Post by adhamsalama »

rubicon33 wrote: post #86
ex-aws-dude wrote: post #36

Its so silly everyone being dependent on a black box like this

You will literally build nothing but the most primitive of devices unless you accept black boxes. In fact I'd argue its one of humanities great strengths that we can build on top of the tools others have built, without having to understand them at the same level it took to develop them.

Those black boxes are usually deterministic.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#363

Post by Schiendelman »

richardjennings wrote: post #266
bcherny wrote: post #209

Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…

I was not aware the default effort had changed to medium until the quality of output nosedived. This cost me perhaps a day of work to rectify. I now ensure effort is set to max and have not had a terrible session since. Please may I have a "always try as hard as you can" mode ?

That's /effort max!

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#364

Post by bcherny »

ctoth wrote: post #256
bcherny wrote: post #209

Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care that went into this. There's a lot here, I will try to break it down a bit. These are the two core things happening: > `redact-thinking-2026-02-12` This beta header hides thinking from th…

[flagged]

Christopher, would you be able to share the transcripts for that repo by running /bug? That would make the reports actionable for me to dig in and debug.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#365

Post by stavros »

lambda wrote: post #282
ctoth wrote: post #256

Earlier quoted context omitted.

[flagged]

I guess one of the things I don't understand: how you expect a stochastic model, sold as a proprietary SaaS, with a proprietary (though briefly leaked) client, is supposed to be predictable in its behavior. It seems like people are expecting LLM based coding to work in a predictable and controllable way. And, well, no, that's not how it works, and especially so when you're using a proprietary SaaS model where you can…

Same as how I expect a coin to come up heads 50% of the time.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#367

Post by TeMPOraL »

malfist wrote: post #270
quietsegfault wrote: post #260

Earlier quoted context omitted.

I’m not sure being confrontational like this really helps your case. There are real people responding, and even if you’re frustrated it doesn’t pay off to take that frustration out on the people willing to help.

Is somebody saying "you're holding it wrong" a "people willing to help"?

They are if you are, in fact, holding it wrong.

As was the usual case in most of the few years LLMs existed in this world.

Think not of iPhone antennas - think of a humble hammer. A hammer has three ends to hold by, and no amount of UI/UX and product design thinking will make the end you like to hold to be a good choice when you want to drive a Torx screw.

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#368

Post by cvandyke »

I am a heavy user of Claude Code building enterprise software. I have not seen these issues and have been extremely productive with CC. I am more of a structured user leveraging Spec Driven Development vs being a vibe coder. I wonder if that is what has helped me not run into these issues

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#369

Post by dev_l1x_be »

lambda wrote: post #282
ctoth wrote: post #256

Earlier quoted context omitted.

[flagged]

I guess one of the things I don't understand: how you expect a stochastic model, sold as a proprietary SaaS, with a proprietary (though briefly leaked) client, is supposed to be predictable in its behavior. It seems like people are expecting LLM based coding to work in a predictable and controllable way. And, well, no, that's not how it works, and especially so when you're using a proprietary SaaS model where you can…

The problem is degradation. It was working much better before. There are many people (some example of a well know person[0]), including my circle of friends and me who were working on projects around the Opus 4.6 rollout time and suddenly our workflows started to degrade like crazy. If I did not have many quality gates between an LLM session and production I would have faced certain data loss and production outages just like some famous company did. The fun part is that the same workflow that was reliably going through the quality gates before suddenly failed with something trivial. I cannot pinpoint what exactly Claude changed but the degradation is there for sure. We are currently evaling alternatives to have an escape hatch (Kimi, Chatgpt, Qwen are so far the best candidates and Nemotron). The only issue with alternatives was (before the Claude leak) how well the agentic coding tool integrates with the model and the tool use, and there are several improvements happening already, like [1]. I am hoping the gap narrows and we can move off permanently. No more hoops, you are right, I should not have attempted to delete the production database moments.

https://x.com/theo/status/2041111862113444221

https://x.com/_can1357/status/2021828033640911196

Re: Issue: Claude Code is unusable for complex engineering tasks with Feb updates

#370

Post by JohnMakin »

wonnage wrote: post #335
JohnMakin wrote: post #297

Earlier quoted context omitted.

I’ve seen you/anthropic comment repeatedly over the last several months about the “thinking” in similar ways - “most users dont look at it” (how do you know this?) “our product team felt it was too visually noisy” etc etc. But every time something like this is stated, your power users (people here for the most part) state that this is dead wrong. I know you are repeating the corporate line here, but it’s bs.

Anecdotally the “power users” of AI are the ones who have succumbed to AI psychosis and write blog posts about orchestrating 30 agents to review PRs when one would’ve done just fine. The actual power users have an API contract and don’t give a shit about whatever subscription shenanigans Claude Max is pulling today

Uh, no. Definitely not me at all.
Post reply on HN