Earlier quoted context omitted.
presumably whatever the top model uses and then some, since the human can use the model. I wonder if a model could score higher if it had a human at its disposal?
Maybe models should ask for human-in-the-loop input, as a matter of convention.
Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
41–50 of 130 posts
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#42This makes so much sense as to why I've always felt that Opus 4.8 was leagues ahead of GPT 5.5. It's so good at taking underspecified requirements and filling in the gaps with sensible approaches for your project
There's specific tasks that Opus does better on like Frontend Dev and Design but for anything else 5.5 just laps it.
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#43The "tasteful solves" is codified cargo culting. The software industry has a tendency to anthropomorphize software while playing to the ego of the programmer. The programmer imagines they are creating a "beautiful" artistic expression. Good code becomes "tasteful", as a software artist must have "good taste" to tell the good software from the bad software. Good quality lacks "bad smells", because a good artist has fi…
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#44I saw on Twitter that in an ML course at Tsinghua University, one of the tests asks students to write quizzes that fail the most LLM models as possible. What if we create a benchmark that works like this and assigns ELO scores? Models fight head-to-head by writing a question, a bug, or an incomplete implementation, which the opponent has to answer, fix, or finish.
In class you'd probably want a rule saying at least one LLM should be able to figure out the answer, but in a head-to-head I'm not sure how to solve it.
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#45Top solve rate is currently 24% with Opus 4.8... What's a competent human supposed to score?
presumably whatever the top model uses and then some, since the human can use the model. I wonder if a model could score higher if it had a human at its disposal?
In all seriousness though, adding capabilities should not normally reduce the effectiveness of a model (within reason: don't pollute the context window with millions of useless tools).
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#46This makes so much sense as to why I've always felt that Opus 4.8 was leagues ahead of GPT 5.5. It's so good at taking underspecified requirements and filling in the gaps with sensible approaches for your project
Man I don't know if I'm living in a crazy bubble or something but GPT 5.5 is lightyears better than Opus 4.8 for me to the point where I'm honestly wondering how you're evaluating them or what kind of work you're doing. There's specific tasks that Opus does better on like Frontend Dev and Design but for anything else 5.5 just laps it.
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#47I saw on Twitter that in an ML course at Tsinghua University, one of the tests asks students to write quizzes that fail the most LLM models as possible. What if we create a benchmark that works like this and assigns ELO scores? Models fight head-to-head by writing a question, a bug, or an incomplete implementation, which the opponent has to answer, fix, or finish.
We could call this "generative adversarial network" (GAN) :) https://en.wikipedia.org/wiki/Generative_adversarial_network
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#48I saw on Twitter that in an ML course at Tsinghua University, one of the tests asks students to write quizzes that fail the most LLM models as possible. What if we create a benchmark that works like this and assigns ELO scores? Models fight head-to-head by writing a question, a bug, or an incomplete implementation, which the opponent has to answer, fix, or finish.
How do you prevent degenerate strategies? I could trivially give a model a SHA256 hash and ask it to provide the source input. In class you'd probably want a rule saying at least one LLM should be able to figure out the answer, but in a head-to-head I'm not sure how to solve it.
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#49Earlier quoted context omitted.
Why supply underspecified requirements in the first place? Both models are good at challenging assumptions/edge cases and asking questions to clarify, but seemingly only when explicitly asked (i.e. something like a "brainstorm" skill). I don't think either harnesses do enough to encourage the model to challenge all assumptions and ask questions, maybe because users might find it annoying. That step is basically a req…
> Why supply underspecified requirements in the first place? Minimizes effort, is the obvious answer.
I think the reason claude has so much mindshare is exactly because it’s more useful to non-developers who wouldn’t know how to describe what an api call executes to his grandmother.
For those who can, I can’t find much of a difference between them. Codex has the slight edge, but that’s all just “feels” to me.
Re: Senior SWE-Bench: open-source benchmark that assesses agents as senior engineers
#50Top solve rate is currently 24% with Opus 4.8... What's a competent human supposed to score?
I'm more interested in how fable would do