J
Justin Lo
@loresjpg · 01:37
Nice DeepSWE score! Does it survive a lowercase filename?
Introducing MaxxBench: 89 DeepSWE tasks with small changes to the instructions or starting code. Same engineering problem, slightly different requirement.
Models clustered around 74% on DeepSWE end up 23 pp apart.
Good
Qui l'a repris
Ce qu'ils en ont dit
J
Julian Schrittwieser
@Mononofu
a cité
· 01:37
Making novel variations of evals is very useful, public evals tend to get memorized!
Hamel Husain
@HamelHusain
a cité
· 01:16
I see some are drawing the wrong inference from this study: they are focusing on this meta benchmark as yet another benchmark for model picking, i.e. open vs closed models, model families etc.
That’s too narrow of an interpretation! You need to do your own private evals on
Teortaxes▶️ (DeepSeek 推特🐋铁粉 2023 – ∞)
@teortaxesTex
a cité
· 08/11 22:00
holy shit, an art form of scientific grift
next METR/Epoch/AA employee right here
you all need to work on your epistemic hygiene
Ben (no treats)