Live data from Hacker News

Claude Sonnet 4.5

anthropic.com

571–580 of 819 posts

Re: Claude Sonnet 4.5

#571
I didn't try the checkpoints, I use local git + /resume from a chat that I pick closer to the git version I restore if Claude screws up.

Will this checkpoint help with chat memory and disregard the latest chat's info?

I use WSL under Windows, VSCode with the WSL plugin, and Claude-Code installed on Ubuntu 24. It is generally solid and has no issue with this setup.

Re: Claude Sonnet 4.5

#572
post #537

Earlier quoted context omitted.

If anything is depressing, it's the amount of people who think these models actually "can code". Because they can't. Also, Clean Code is a really bad ideology, you should regret wasting time on it regardless of LLM code generation.

You just called yourself out- I don't think most people are aware of a "Clean Code" handbook. I had to google it. When most people think of "clean code", they are not thinking about whatever got you so worked up.

The fact that he capitalized both Cs indicates he's talking about the book, which is famous enough that I learned about it and its influence when I was in school ~15 years ago.

GP wrote clean code (lowercase) which most people would take to mean the general practices of hygenic, well maintained code.

Re: Claude Sonnet 4.5

#573
post #199

I am a paying subscriber to Gemini, Claude and OpenAI. I don't know if it's me, but over the last few weeks I've got to the conclusion ChatGPT is very strongly leading the race. Every answer it gives me is better - it's more concise and more informative. I look forward to testing this further, but out of the few runs I just did after reading about this - it isn't looking much better

What about Grok, are they catching up?

Grok 4 is extremely capable, but for everyday chatting, Grok kinda sucks since it keeps repeating what you told it, and saying the current timestamp for some reason. ChatGPT is much better with its post training and prompt I feel like.

Re: Claude Sonnet 4.5

#574
post #537

Earlier quoted context omitted.

If anything is depressing, it's the amount of people who think these models actually "can code". Because they can't. Also, Clean Code is a really bad ideology, you should regret wasting time on it regardless of LLM code generation.

You just called yourself out- I don't think most people are aware of a "Clean Code" handbook. I had to google it. When most people think of "clean code", they are not thinking about whatever got you so worked up.

Clean code is over abstraction, spaghetti code. The people who are part of this cult just point to the source material and title, never critically think about why it might be bad (it’s super slow, check YouTube “clean code performance” for why) or entertain alternatives.

Re: Claude Sonnet 4.5

#575
post #564

Earlier quoted context omitted.

> This is the future we live in. It's just a bug. Chill. Wait a business day and try again. You write as if you've never experienced a bug before.

If you’re being sarcastic, you might want to edit your post to make that clearer.

You're absolutely right!

Re: Claude Sonnet 4.5

#576
post #542

It is time to acknowledge that AI coding does not actually work. ok, you think it's a promising field and you want to explore it, fine. Go for it. Just stop pretending that what these models are currently doing is good enough to replace programmers. I use LLMs a lot, even for explaining documentation. I used to use them for writing _some_ code, but I have never ever gotten a code sample over 10 lines that was not in…

Very interesting observation. I haven’t written a function by hand in 18 months.

Can you show me a sample of the code you have AI write for you?

Re: Claude Sonnet 4.5

#577

> Practically speaking, we’ve observed it maintaining focus for more than 30 hours on complex, multi-step tasks. Really curious about this since people keep bringing it up on Twitter. They mention it pretty much off-handedly in their press release and doesn't show up at all in their system card. It's only through an article on The Verge that we get more context. Apparently they told it to build a Slack clone and left…

This is obviously much more than just taking an LLM an letting it run for 30 hours. You have to build a whole environment together with external tool integration and context management and then tune the prompts and perhaps even set up a multi-agent system. I believe that if someone puts a ton of work into this you can have an LLM run for that long and still produce sellable outputs, but let's not pretend like this is…

Claude Code with a good prompt can run for hours.

Re: Claude Sonnet 4.5

#578

> Practically speaking, we’ve observed it maintaining focus for more than 30 hours on complex, multi-step tasks. Really curious about this since people keep bringing it up on Twitter. They mention it pretty much off-handedly in their press release and doesn't show up at all in their system card. It's only through an article on The Verge that we get more context. Apparently they told it to build a Slack clone and left…

Curious about this too – does it use the standard context management tools that ship with Claude Code? At 200K context size (or 1M for the beta version), I'm really interested in the techniques used to run it for 30 hours.

Sub-agents. I've had Claude Code run a prompt for hours on end.

Re: Claude Sonnet 4.5

#579

When I see how much the latest models are capable of it makes me feel depressed. As well as potentially ruining my career in the next few years, its turning all the minutiae and specifics of writing clean code, that I've worked hard to learn over the past years, into irrelivent details. All the specifics I thought were so important are just implementation details of the prompt. Maybe I've got a fairly backwards view…

It's not wasted imo. Llms don't get 'it'. They can't tell what's truely good. You have to guide them. To do that you have to know what your doing.

Re: Claude Sonnet 4.5

#580

Earlier quoted context omitted.

The benchmarks are not typically ongoing, we do not often see comparisons between week 1 and week 8. Sprinkle a bit of training on the benchmarks in and you can ensure higher scores for the next model. A perfect scam loop to keep the people happy until they wise up.

> The benchmarks are not typically ongoing, we do not often see comparisons between week 1 and week 8 You don't need to compare "A (Week 1)" to "A (Week 8)" to be able to show "B (Week 1)" is genuinely x% better than "A (Week 1)".

As I said sprinkle a bit of benchmarks polluting the training and you have your loop. Each iteration will be better at benchmarks if that's the goal and that goal/context reinforces.
Post reply on HN