Live data from Hacker News

Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

blog.can.ac

221–230 of 318 posts

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#221
post #170

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…

> “replace line 2:f1, replace range 1:a3 through 3:0e, insert after 3:0e.” Not sure what they're calculating, but this seems to me like it could be many times more efficient than 20%.

Yes, this looks like O(1) actions, where before, its likely that harnesses are ingesting and outputting huge portions of the source files for each step, and the local uses of str_replace() are themselves O(N) on the users computer. The excess reads and writes from the LLM are O(N^2).

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#222

I 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…

Ive been working on Peen, a CLI that lets local Ollama models call tools effectively. It’s quite amateur, but I’ve been surprised how spending a few hours on prompting, and code to handle responses, can improve the outputs of small local models.

https://github.com/codazoda/peen

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#223

Earlier quoted context omitted.

Make a CLI tool for it, of course

What? Why? What advantage does that have over just using an MCP server that exposes tools to run queries?

Context.

Why would I use an MCP when I can use a cli tool that the model likely trained on how to use?

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#224

I 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…

Ive been working on Peen, a CLI that lets local Ollama models call tools effectively. It’s quite amateur, but I’ve been surprised how spending a few hours on prompting, and code to handle responses, can improve the outputs of small local models. https://github.com/codazoda/peen

Very cool. Love to see more being squeezed from smaller models.

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#225

Earlier quoted context omitted.

As a VC in 2026 I'm going to be asking every company "but what's your harness strategy?"

Given that you're likely in San Francisco, make sure you say "AI Harness".

It’s all about user-specific bindings.

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#226

I 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…

Ive been working on Peen, a CLI that lets local Ollama models call tools effectively. It’s quite amateur, but I’ve been surprised how spending a few hours on prompting, and code to handle responses, can improve the outputs of small local models. https://github.com/codazoda/peen

[deleted]

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#227

Earlier quoted context omitted.

Em dashes are used often by LLMs, because humans use them often. On mac keyboards its easily typed. I know this is oversimplifying the situation, but I don't see the usefulness of the constant witch-hunting for allegedly LLM-generated text. For text we are long beyond the point, where we can differenciate between human generated and machine generated. We're even at the point, where it gets somewhat hard to identify m…

Yeah, I agree with you. I'm so tired of people complaining about AI-generated text without focusing on the content. Just don't read it if you don't like it. It's another level of when people complain how a website is not readable for them or some CSS rendering is wrong or whatever. How does it add to the discussion?

The problem is that there’s infinite “content” out there.

The amount of work the author puts in is correlated with the value of the piece (insight/novelty/etc). AI-written text is a signal that there’s less less effort and therefore less value there.

It’s not a perfect correlation and there are lots of exceptions like foreign language speakers, but it is a signal.

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#228
post #20

Earlier quoted context omitted.

At this point subsidizing Chinese open-weights vendors by paying for them is just the right thing to do. Maybe they too might go closed-weights when they become SotA, but they're now pretty close and haven't done it.

I am wondering what kinds of harness are best for GLM, Deepseek, Qwen, Kimi.

OpenCode with Kimi has been great for me.

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#229
post #71

I 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…

[flagged]

Honestly responses like this should just be straight blocked by the moderators. They are so super lame and go directly against the rules.

Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

#230
post #178

I 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…

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…

I am in the same boat. I have built bunch of bash/shell scripts in a folder back in 2022/2023. When models first came out, I would prompt them to use subshell syntax to call commands (ie: '$(...)' format)

I would run it via calling AWS Bedrock API through AWS-CLI. Self iterating and simple. All execution history directly embedded within.

Soon after, I wrote a help switch/command to each script. Such that they act as like MCP. To this day, they outperform any prompts one can make.

Post reply on HN