Live data from Hacker News

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

github.com

401–410 of 829 posts

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

#401
post #282
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…

> how you expect a stochastic model [...] is supposed to be predictable in its behavior.

I used it often enough to know that it will nail tasks I deem simple enough almost certainly.

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

#402
I haven't noticed any issues on well-specified tasks, even ones requiring large amounts of thinking.

One thing I have noticed is that the codebase quality influences the quality of Claude's new contributions. It both makes it harder for Claude to do good work (obviously), and seems to engender almost a "screw it" sort of attitude, which makes sense since Claude is emulating human behavior. Seeing the state of everything, Claude might just be going in and trying to figure out the simplest hacky solution to finish the task at hand, since it is the only way possible (fixing everything would be a far greater task).

Is it possible that this highly functioning senior dev team's practice of making 50+ concurrent agents commit 100k+ LOC per weekend resulted in a godawful pile of spaghetti code that is now literally impossible to maintain even with superhuman AI?

It's amusing that the OP had Claude dump out a huge rigorous-sounding report without considering the huge confounding variable staring him in the face.

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

#405

Earlier quoted context omitted.

Yeah so? Claude isn't an OS. It's the thing making my code. I don't want my codebase to be some bytecode adjacent thing that LLMs operate on.

So you stand upon a big pile of black boxes.

Black boxes aren't inherently bad. But if they don't have well defined mappings of inputs to outputs, they aren't good black boxes. That's the problem with Claude Code imo.

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

#406

Earlier quoted context omitted.

Uh, no. Definitely not me at all.

[flagged]

Whatever makes you feel better about yourself, I guess. My account history on this topic is pretty easily searchable, but I guess it's easier to make driveby comments like this than be informed.

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

#407
post #392

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

[dead]

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

#408
post #174

Earlier quoted context omitted.

Make sure to use "PRETTY PLEASE" in all caps in your `SOUL.md`. And occasionally remind it that kittens are going to die unless it cooperates. Works wonders.

Can you paste the relevant section in your soul please?

Sure, as soon as I locate my soul.

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

#409

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

It's to prevent distillation. Duh

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

#410
post #373

Earlier quoted context omitted.

Piece of free advice towards a better civilisation: people who didn't even read the comment they're replying to shouldn't be rewarded for their laziness.

I read his comment and still replied. I think his claim that nobody reads thinking blocks and that thinking blocks increase latency is nonsense. I am not going to figure out which settings I need to enable because after reading this thread I cancelled my subscription and switched over to Codex. Because I had the exact same experience as many in this thread. Also what is that "PR advice"—he might as well wear a suit.…

Alright, I just tested that setting and it doesn't work.

https://i.imgur.com/MYsDSOV.png

I tested because I was porting memories from Claude Code to Codex, so I might as well test. I obviously still have subscription days remaining.

There is another comment in this thread linking a GitHub issue that discusses this. The GitHub issue this whole HN submission is about even says that Anthropic hides thinking blocks.

Post reply on HN