Benchmarking Opus 5 on SlopCodeBench
51–60 of 131 posts
Re: Benchmarking Opus 5 on SlopCodeBench
#52Nice! I actually ran across this paper+benchmark recently, too. It's the first I've found that start to aim at some of the non-functional and longitudinal requirements that I think have always been an important part of writing production code. It's especially relevant now that models are good enough to solve ~most point-in-time problems. Some relevant but disconnected thoughts: - deterministic scores are so nice - wh…
State space of a system AND the way to make it accessible / visible to a model. Many times a model can work magic if it can "see" the state of a system in a way that suits it. That's why sometimes having a cli added to the environment seems like such a big unlock. Because that cli usually takes a complex state and allows visibility into it, and possible manipulation in a structured way.
Re: Benchmarking Opus 5 on SlopCodeBench
#53This matches my experience of Opus 5 being a nice improvement over Opus 4.8, but not being revolutionary like Fable felt. I’ve now replaced my use of Opus 4.8 xhigh with Opus 5 medium, and I’m using less tokens and it’s quicker. I can understand people being annoyed by its writing style but for getting work done that really doesn’t bother me. I’ve been really enjoying using it.
I think they neutered Fable. When it first came out it was indeed revolutionary. But what we have today, is not what we had before the ban.
Re: Benchmarking Opus 5 on SlopCodeBench
#54I still don't have access to Opus 5. I'm on the latest version from Homebrew, I guess the update hasn't made it there yet
Re: Benchmarking Opus 5 on SlopCodeBench
#55I have found that models are generally poor at managing refactors / complexity while also implementing new features. But I’ve had some success with a semi-lights-off approach where you decompose it and prompt the model adversarially in a second pass to look for new rough edges and areas of complexity or refactors that might simplify the codebase.
So I’d be very curious to see this benchmark but with something like a periodic “refactor turn” interleaved in.
Also eager to see Fable benchmarked; anecdotally that was the only model whose code I felt I could actually trust to not review closely.
Re: Benchmarking Opus 5 on SlopCodeBench
#56Re: Benchmarking Opus 5 on SlopCodeBench
#57Earlier quoted context omitted.
I’ve observed the degradation, but I suspect what’s happening is they’re tuning it for lower inference costs. Maybe turning down the amount of thinking, maybe quantizing, maybe something else. It seems like there’s a week by week and sometimes day by day change in performance when on a subscription plan using their harnesses.
https://marginlab.ai/trackers/claude-code/ their tracker generally shows that isn’t the case. The only times I’ve seen it drop is something broken and just before fable launched.
Re: Benchmarking Opus 5 on SlopCodeBench
#58Re: Benchmarking Opus 5 on SlopCodeBench
#59a 41% improvement is not much higher? come on that's just doomer
Re: Benchmarking Opus 5 on SlopCodeBench
#60I still don't have access to Opus 5. I'm on the latest version from Homebrew, I guess the update hasn't made it there yet