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

381–390 of 829 posts

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

#381

Post by geysersam »

wonnage wrote: post #326
ctoth wrote: post #274

Earlier quoted context omitted.

Fair point on tone. It's a bit of a bind isn't it? When you come with a well-researched issue as OP did, you get this bland corporate nonsense "don't believe your lyin' eyes, we didn't change anything major, you can fix it in settings." How should you actually communicate in such a way that you are actually heard when this is the default wall you hit? The author is in this thread saying every suggested setting is alr…

Just use a different tool or stop vibe coding, it’s not that hard. I really don’t understand the logic of filing bug reports against the black box of AI

People file tickets against closed source "black box" systems all the time. You could just as well say: Stop using MS SQL, just use a different tool, it's not that hard.

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

#382

Post by stefan_ »

koverstreet wrote: post #217
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…

There's been more going on than just the default to medium level thinking - I'll echo what others are saying, even on high effort there's been a very significant increase in "rush to completion" behavior.

Theres also been tons of thinking leaking into the actual output. Recently it even added thinking into a code patch it did (a[0] &= ~(1 << 2); // actually let me just rewrite { .. 5 more lines setting a[0] .. }).

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

#383

Post by ai_slop_hater »

trvz wrote: post #373
antonvs wrote: post #265

Earlier quoted context omitted.

> As I noted in the comment, Piece of free PR advice: this is fine in a nerd fight, but don't do this in comments that represent a company. Just repeat the relevant information.

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. This is absolutely a nerd fight.

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

#384

Post by try-working »

aizk wrote: post #214
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…

How do you guys manage regressions as a whole with every new model update? A massive test set of e2e problem solving seeing how the models compare?

I use a self-documenting recursive workflow: https://github.com/doubleuuser/rlm-workflow

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

#385

Post by enraged_camel »

ctoth wrote: post #274
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.

Fair point on tone. It's a bit of a bind isn't it? When you come with a well-researched issue as OP did, you get this bland corporate nonsense "don't believe your lyin' eyes, we didn't change anything major, you can fix it in settings." How should you actually communicate in such a way that you are actually heard when this is the default wall you hit? The author is in this thread saying every suggested setting is alr…

I read the entire performance degradation report in the OP, and Boris's response, and it seems that the overwhelming majority of the report's findings can indeed be explained by the `showThinkingSummaries` option being off by default as of recently.

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

#387

Post by ianberdin »

I use it ultra extensively and it works absolutely fantastic. Sometimes I think: "people are right, it is worse now" and then realize it is mistake, poor context or poor prompt. Garbage in, garbage out. No, it works not worse, but better.

I built entire AI website builder https://playcode.io using it, alone. 700K LOKs total. It also uses Opus. So believe me, I know how it works. Trick is simple: never ever expect it finds necessary files. Always provide yourself. Always.

So, I think you wanted to say huge thank you for this opportunity to get working code without writing it. Insane times, insane.

Huge thanks for 1M context window included to Max subscription.

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

#388

Post by thiht »

ex-aws-dude wrote: post #36

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

It’s not so much the black box that’s the issue here, but the fact you can’t even make sure doesn’t change. I’d be fine with downloading the black box and running it on my servers until I decide to update it.

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

#389

Post by aktenlage »

onlyrealcuzzo wrote: post #115
summarity wrote: post #8

Not claude code specific, but I've been noticing this on Opus 4.6 models through Copilot and others as well. Whenever the phrase "simplest fix" appears, it's time to pull the emergency break. This has gotten much, much worse over the past few weeks. It will produce completely useless code, knowingly (because up to that phrase the reasoning was correct) breaking things. Today another thing started happening which are…

> Whenever the phrase "simplest fix" appears, it's time to pull the emergency break. Second! In CLAUDE.md, I have a full section NOT to ever do this, and how to ACTUALLY fix something. This has helped enormously.

Where is that? I found "Return the simplest working solution. No over-engineering." which sounds more like the simplest fix.

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

#390

Post by joshribakoff »

> We exclusively use 1M internally, so we're dogfooding it all day

That is so out of touch. Customers do not exclusively use 1M. This is like a fronted developer shipping tons of unused Mb and being oblivious because they are on fast internet themselves.

Post reply on HN