If you run this out, you realize that the Worse is Better paradox has inverted, it's an arbitrage, and the race is on.
Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
111–120 of 318 posts
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#112On first principles it would seem that the "harness" is a myth. Surely a model like Opus 4.6/Codex 5.3 which can reason about complex functions and data flows across many files would trip up over top level function signatures it needs to call? I see a lot of evidence to the contrary though. Anyone know what the underlying issue here is?
Like a good programming language, a good harness offers a better affordance for getting stuff done.
Even if we put correctness aside, tooling that saves time and tokens is going to be very valuable.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#113Back when I was maintaining a coding harness around the time of Claude 3.5 we tried hash prefixes we tried line number prefixes we tried a lot of different approaches to making the model better at selecting edit blocks and ultimately at-least then fuzzy string matching won out.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#114Shows how much room for improvement there is on the harness level. Agents waste a lot of tokens on editing, sandboxes, passing info back and forth from tool calls and subagents. Love the pragmatic mix of content based addressing + line numbers. Beautiful.
Indeed. The biggest waste might be the overuse of MCP for everything. Sure it makes the initial development easier but then for every connection you're using a hundred billion dollar parameter model to decide how to make the call when it's usually completely unnecessary and then prone to random errors. MCP is the hammer that can make literally everything look like a nail...
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#115Earlier quoted context omitted.
Which, IMHO, should be why we should be able to change them freely or make our own. Being locked into a specific harness because you pay 20 bucks per month vs. pay-per-use ... is kinda dumb.
> Being locked into a specific harness because you pay 20 bucks per month vs. pay-per-use ... is kinda dumb. I’ll probably get downvoted for this, but am I the only one who thinks it’s kind of wild how much anger is generated by these companies offering discounted plans for use with their tools? At this point, there would be less anger and outrage on HN if they all just charged us the same high per-token rate and off…
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#116Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#117On first principles it would seem that the "harness" is a myth. Surely a model like Opus 4.6/Codex 5.3 which can reason about complex functions and data flows across many files would trip up over top level function signatures it needs to call? I see a lot of evidence to the contrary though. Anyone know what the underlying issue here is?
It's completely understandable that prompting in better/more efficient means would produce different results.
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#118> Treating harnesses as solved, or even inconsequential, is very short-sighted Is it possible that burning extra tokens is the point, since they get paid more?
Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#119Re: Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed
#120Earlier quoted context omitted.
Because I like them?
reminds me of that one guy complaining that everyone is calling them an AI when AI was trained on their grammar style.