Seems like a very cool technique, but also very oversold. He's seeing a 5% improvement on a find and replace benchmark of his own devising and saying stuff like this in the blog post: > Here is why that is backwards. I just showed that a different edit format improves their own models by 5 to 14 points while cutting output tokens by ~20%. That’s not a threat. It’s free R&D. He makes it sounds like he got a 5-14% boos…
> That’s not a threat. It’s free R&D. That's not a human. It's AI slop.
Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
241–250 of 318 posts
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#242Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#243Seems like a very cool technique, but also very oversold. He's seeing a 5% improvement on a find and replace benchmark of his own devising and saying stuff like this in the blog post: > Here is why that is backwards. I just showed that a different edit format improves their own models by 5 to 14 points while cutting output tokens by ~20%. That’s not a threat. It’s free R&D. He makes it sounds like he got a 5-14% boos…
> That’s not a threat. It’s free R&D. That's not a human. It's AI slop.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#244Getting banned from Gemini while attempting to improve Gemini is the most Googley thing ever :D imagine letting your automated "trust and safety" systems run amok so that they ban the top 0.01% of your users with no recourse. Google really knows how score an own-goal.
I really don't understand what is his usage pattern would have triggered that obviously automated ban. Can somebody let me know what they might think is adversarial enough to be considered 'hacking' or similar by a bot?
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#245It had some bugs around whitespace replacements but the model seems happy with it now.
Thanks and keep it up! Shoutout to @jahala for tilth as well.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#246I just saw a [paper](https://arxiv.org/pdf/2602.05447) that investigated similar aspects of TOON (which aims to reduce JSON tokens), and they found that even though TOON itself reduced the number of tokens, LLMs were less familiar with it, and thus spent even more tokens trying to decipher it, or making mistakes (see section 4.5, figures 6 and 7).
From the paper: >Unlike Markdown, where each grep hit simply returned more text, TOON's overhead was driven by a combination of output density and additional tool calls from pattern unfamiliarity
---- There's a strangeness tax with LLMs, and it can be substantial.
I would not be surprised at all if this technique turned out to be only a local minimum, with detrimental global effects.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#247I really enjoyed this article. I think the author is precisely right and I've been saying this for a long time. There's a ton of extremely interesting low hanging fruit that can vastly improve the effectiveness of even currently existing models hiding in how we design our agent harnesses; enough to — at least until we hit diminishing returns — make as much or more of a difference than training new models! I think one…
Also, yes, I'm aware that I use a lot of "its not just X, its Y." I promise you this comment is entirely human written. I'm just really tired and tend to rely on more wrote rhetorical tropes when I am. Believe me, I wrote like this long before LLMs were a thing.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#248Earlier quoted context omitted.
My Weird Hill is that we should be building things with GPT-4. I can say unironically that we haven't even tapped the full potential of GPT-4. The original one, from 2023. With no reasoning, no RL, no tool calling, no structured outputs, etc. (No MCP, ye gods!) Yes, it's possible to build coding agents with it! I say this because I did! Forcing yourself to make things work with older models forces you to keep things…
> semantic > grep def Once you get to a codebase beyond a certain size, that no longer works. I've for one found Serena https://github.com/oraios/serena , which you can install from right within Claude, to be a fairly fantastic code-interaction tool for LLM's. Both semantic search as well as editing. And with way less token churn.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#249Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#250In this era, we should build these kinds of tools for problems we know are straightforward ones you can’t get smarter than, even as intelligence continues to advance. Using tools like "bash" or command-line interfaces originally designed for humans is a good initial approach, since we can essentially reuse much of what was built for human use. Later, we can optimize specifically for machines, either accounting for their different cognitive structures (e.g., the ability to memorize extremely long contexts compared to humans) or adapting to the stream-based input/output patterns of current autoregressive token generators.
Eventually, I believe machine intelligence will build their own tools based on these foundations, likely a similar kind of milestone to when humans first began using tools.