News for hackers. Stuff that matters.
Re:Claude Code Daily Benchmarks for Degradation Tracking by mohsen1 on Thursday January 29, 2026 @10:18AM (#46811344)
Hope you don't mind the unrelated question:

How do you pay for those SWE-bench runs?

I am trying to run a benchmark but it is too expensive to run enough runs to get a fair comparison.

https://mafia-arena.com

Re:Claude Code Daily Benchmarks for Degradation Tracking by ofirpress on Thursday January 29, 2026 @10:22AM (#46811406)
Benchmarks can get costly to run- you can reach out to frontier model creators to try and get them to give you free credits, but usually they'll only agree to that once your benchmark is pretty popular.
Re:Claude Code Daily Benchmarks for Degradation Tracking by Dolores12 on Thursday January 29, 2026 @10:38AM (#46811596)
so basically they know requests using your API key should be treated with care?
Re:Claude Code Daily Benchmarks for Degradation Tracking by swyx on Thursday January 29, 2026 @02:18PM (#46815102)
they could but you can also have some trust in anthropic to have some integrity there, these are earnest people.

"trust but verify" ofc . https://latent.space/p/artificialanalysis do api keys but also mystery shopper checks

Re:Claude Code Daily Benchmarks for Degradation Tracking by mrandish on Thursday January 29, 2026 @04:16PM (#46816707)
> these are earnest people.

I agree.

I'll also add that when my startup got acquired into a very large, well-known valley giant with a sterling rep for integrity and I ended up as a senior executive - over time I got a first-hand education on the myriad ways genuinely well-intentioned people can still end up being the responsible party(s) presiding over a system doing net wrong things. All with no individual ever meaning to or even consciously knowing.

It's hard to explain and I probably wouldn't have believed myself before I saw and experienced it. I'm pretty sure I ended up moving on before I compromised myself but preventing that required constant vigilance and led to some inter-personal and 'official' friction. Standing against an overwhelming organizational tide is stressful and never leads to popularity or promotion.

Re:Claude Code Daily Benchmarks for Degradation Tracking by pluralmonad on Thursday January 29, 2026 @05:10PM (#46817454)
Someone posted this here the other day and it uses _Demons_ to discuss exactly your point.

https://possessedmachines.com/

Re:Claude Code Daily Benchmarks for Degradation Tracking by mrandish on Thursday January 29, 2026 @05:48PM (#46817948)
Wow. Only one page in and already bookmarked to absorb later. Thanks for the link.
Re:Claude Code Daily Benchmarks for Degradation Tracking by debugnik on Friday January 30, 2026 @02:49AM (#46821638)
That's why we're setting up adversarial benchmarks to test if they are doing the thing they promised not to do, because we totally trust them.
Re:Claude Code Daily Benchmarks for Degradation Tracking by epolanski on Thursday January 29, 2026 @10:50AM (#46811787)
The last thing a proper benchmark should do is reveal it's own API key.
Re:Claude Code Daily Benchmarks for Degradation Tracking by sejje on Thursday January 29, 2026 @11:17AM (#46812267)
That's a good thought I hadn't had, actually.
Re:Claude Code Daily Benchmarks for Degradation Tracking by plagiarist on Thursday January 29, 2026 @11:58AM (#46812867)
IMO it should need a third party running the LLM anyway. Otherwise the evaluated company could notice they're receiving the same requests daily and discover benchmarking that way.
Re:Claude Code Daily Benchmarks for Degradation Tracking by jabedude on Thursday January 29, 2026 @01:08PM (#46813971)
But that's removing a component that's critical for the test. We as users/benchmark consumers care that the service as provided by Anthropic/OpenAI/Google is consistent over time given the same model/prompt/context
Re:Claude Code Daily Benchmarks for Degradation Tracking by plagiarist on Thursday January 29, 2026 @03:21PM (#46816020)
Might as well have the free tokens, then, especially if it is an open benchmark they are already aware of. If they want to game it they cannot be stopped from doing so when it's on their infra.
Re:Claude Code Daily Benchmarks for Degradation Tracking by mrandish on Thursday January 29, 2026 @05:32PM (#46817735)
With the insane valuations and actual revenue at stake, benchmarkers should assume they're assessing in an adversarial environment. Whether from intentional gaming, training to the test, or simply from prioritizing things likely to make results look better, targeting benchmarks will almost certainly happen.

We already know large graphics card manufacturers tuned their drivers to recognize specific gaming benchmarks. Then when that was busted, they implemented detecting benchmarking-like behavior. And the money at stake in consumer gaming was comparatively tiny compared to current AI valuations. The cat-and-mouse cycle of measure vs counter-measure won't stop and should be a standard part of developing and administering benchmark services.

Beyond hardening against adversarial gaming, benchmarkers bear a longer term burden too. Per Goodhart's Law, it's inevitable good benchmarks will become targets. The challenge is the industry will increasingly target performing well on leading benchmarks, both because it drives revenue but also because it's far clearer than trying to glean from imprecise surveys and fuzzy metrics what helps average users most. To the extent benchmarks become a proxy for reality, they'll bear the burden of continuously re-calibrating their workloads to accurately reflect reality as user's needs evolve.

Re:Claude Code Daily Benchmarks for Degradation Tracking by mohsen1 on Thursday January 29, 2026 @10:23AM (#46811418)
yes I reached out to them but as you say it's a chicken-and-egg problem.

Thanks!