News for hackers. Stuff that matters.
Re:How the Claude Code team thinks about verification by pu_pe on Tuesday November 17, 2026 @07:12AM (#50530359)
> It’s got some very expensive practices, where near-free practices would produce the same or better results.

I think tokens are near-free already, even for those of us outside Anthropic.

More importantly, your philosophy comes from a time where thinking had to be front-loaded: you try to predict everything that can go wrong, then design deterministic tests that can catch those things and a decision tree to figure out what to do in each case. This approach was the only viable way until now, but maybe that will change. Having the equivalent of a senior engineer thoroughly review each error with full context of what the application and feature is trying to achieve could perhaps uncover different insights, or cover edge cases more smoothly.

Re:How the Claude Code team thinks about verification by skydhash on Tuesday November 17, 2026 @07:27AM (#50530492)
> you try to predict everything that can go wrong, then design deterministic tests that can catch those things and a decision tree to figure out what to do in each case

No real software engineer think that way, as things that can go wrong are near infinite. Instead you design the right thing and write tests that verify that it’s indeed the right thing and add some more that are the wrong thing, especially at the edge of definition. Then you rely on the dev to not make very obvious errors like coding something that is not in the requirements or is completely opposite.

Re:How the Claude Code team thinks about verification by jgalt212 on Tuesday November 17, 2026 @07:46AM (#50530672)
As far as timelines go both property based tests and fuzzers predate this token maxing strategy.
Re:How the Claude Code team thinks about verification by bayindirh on Tuesday November 17, 2026 @07:51AM (#50530715)
But they are old, well tested, and not AI based, hence bland.

In this age of AI, anything well understood and effective while being efficient is out. These tokens must be used, atmosphere must be heated.

It's November. Winter is coming.

Re:How the Claude Code team thinks about verification by NewJazz on Tuesday November 17, 2026 @11:05AM (#50533358)
[delayed]
Re:How the Claude Code team thinks about verification by bayindirh on Tuesday November 17, 2026 @11:27AM (#50533807)
Normally it should snow here. I walk around with a t-shirt.

Climate change and global warming is really a scam, they have made it snow with chemtrails in the 80s, it seems.

Though I miss snow and cold. They are not making seasons as they used to anymore. They shouldn't have privatized weather.

(This comment is written by a human, and contains an implicit /s)

Re:How the Claude Code team thinks about verification by skohan on Tuesday November 17, 2026 @08:03AM (#50530816)
It's great to have that option available, but it's incredibly inefficient to just throw GPU hours at a problem that can be solved deterministically.
Re:How the Claude Code team thinks about verification by pydry on Tuesday November 17, 2026 @08:23AM (#50531017)
Good for anthropic margins though.
Re:How the Claude Code team thinks about verification by duskdozer on Tuesday November 17, 2026 @10:21AM (#50532594)
It really seems too lucrative for them to weight the models toward higher token usage and less-deterministic solutions for them not to do it.
Re:How the Claude Code team thinks about verification by castis on Tuesday November 17, 2026 @08:09AM (#50530871)
[delayed]
Re:How the Claude Code team thinks about verification by chrisweekly on Tuesday November 17, 2026 @08:18AM (#50530967)
"non-deterministic" -> "deterministic"

right?

Re:How the Claude Code team thinks about verification by castis on Tuesday November 17, 2026 @08:21AM (#50530999)
yuppp, thank you :D
Re:How the Claude Code team thinks about verification by pu_pe on Tuesday November 17, 2026 @08:35AM (#50531146)
It isn't the same work, though, so the question is whether the added cost is worth it. Yes it costs more, but the price of tokens has fallen 100x in the past two years and it will continue to drop.
Re:How the Claude Code team thinks about verification by Grimburger on Tuesday November 17, 2026 @08:28AM (#50531074)
> tokens are near-free already

How long do you think that will last?

Am over 11 billion tokens this month on a subscription. In API usage its close to $5000 and there's still 13 days left in the month.

Eventually the music in musical chairs stops. Already many anecdotal reports of the always opaque limits being lowered across the board. On a gemini pro account for personal use I can use a weeks worth of Argon in about 20 minutes on agy.

Re:How the Claude Code team thinks about verification by olkre on Tuesday November 17, 2026 @09:06AM (#50531572)
The cost halves every year so far. Current level of llm will get cheaper
Re:How the Claude Code team thinks about verification by curt15 on Tuesday November 17, 2026 @09:15AM (#50531686)
Cost or price? ANT's shareholders and creditors aren't going to wait forever for ROI.
Re:How the Claude Code team thinks about verification by rcxdude on Tuesday November 17, 2026 @09:53AM (#50532190)
Cost. Their margins are still pretty healthy from what they've disclosed.
Re:How the Claude Code team thinks about verification by AYoung010 on Tuesday November 17, 2026 @05:14PM (#50539003)
If you disregard the inflexible and increasing cost of training lol
Re:How the Claude Code team thinks about verification by Grimburger on Tuesday November 17, 2026 @10:02AM (#50532308)
Undoubtedly you are right, except I see it the complete opposite way, companies providing the best models will probably need even more from those willing to pay in the near future, and likely get it from those wanting to ride ahead of the wave.
Re:How the Claude Code team thinks about verification by svnt on Tuesday November 17, 2026 @10:48AM (#50533031)
For the majority of tasks, the best models are no longer required.

Many benchmarks are already saturated today on many tedious tasks still being done by humans across the world. Frontier labs are introducing their own budget options prior to IPO, undercutting their revenue, because otherwise they risk losing seats.

Choosing what to do and how to do it is the actual frontier now and is still not apparently well supported in any model. Current so-called decision models are not decision models, they are available-fact-evaluating models.

Re:How the Claude Code team thinks about verification by Grimburger on Tuesday November 17, 2026 @04:35PM (#50538521)
> Many benchmarks are already saturated today on many tedious tasks

Exactly my point, think the easy things won't even need 3rd party apis in the near future.

But frontier models only seem to need more and more VRAM to keep winning the race. Feel free to look up the cost of running Kimi K3 open weights today, probably the best estimate known publicly, it's hardly a casual affair.

Re:How the Claude Code team thinks about verification by mikeocool on Tuesday November 17, 2026 @04:01PM (#50538123)
Ubers got cheaper and cheaper for a while, until they didn’t.
Re:How the Claude Code team thinks about verification by solatic on Wednesday November 18, 2026 @04:41AM (#50544095)
> How long do you think that will last?

Don't forget that it's a hypothesis, not a foregone conclusion, that this will stop. Part of the question is whether demand will continue to rise. If volume increases sufficiently, you can cut prices and improve profits at the same time, as long as you continue to make a profit at the margin.

Moore's Law kept Intel and competitors pushing R&D budget that pushed perf/watt year after year because the overall computing market just kept growing and growing. The growing demand soaked up everything Intel and co. pushed into the market; the R&D spend helped players retain market share in the face of competition. Why do you think AI is different? R&D into better, faster, cheaper chips brings down the cost of both training and inference over time, and cheaper token cost unlocks additional demand, which justifies more R&D budget, in a virtuous cycle. It continues until there's really no more demand to be unlocked, no more improvements can be made to the chips (i.e. you hit the laws of physics), or there's no more money to be invested (i.e. even capital markets have limits, with only so much cash in circulation, or macro interference like war).

Do we really have any reason to believe that demand will taper off?

Re:How the Claude Code team thinks about verification by NewJazz on Tuesday November 17, 2026 @11:04AM (#50533331)
[delayed]
Re:How the Claude Code team thinks about verification by kuschku on Tuesday November 17, 2026 @02:09PM (#50536587)
Near-free? Even using Claude just for /code-review constantly leads to

> ● Agent "[REDACTED] audit" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "Verify [REDACTED] bug" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "Verify [REDACTED] bug" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "[REDACTED]" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "Verify [REDACTED] injection" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "Verify [REDACTED] regression" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "Verify [REDACTED] race" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "[REDACTED] root-cause" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5) > ● Agent "[REDACTED]" failed: Agent terminated early due to an API error: You've hit your 5-hour limit · resets 10:50pm (Europe/Berlin) (error type rate_limit, HTTP 429, request id [REDACTED], model sent to the API: claude-opus-5-5)

Re:How the Claude Code team thinks about verification by saghm on Tuesday November 17, 2026 @05:44PM (#50539334)
Even if you aren't paying currency, there's still resource consumption in terms of compute, which in turn requires energy, which is priced in data centers based on usage. You're almost literally taxing people in communities near data centers, I guess because it's cooler to do it this way?