HN user

gavmor

923 karma

meet.hn/city/us-Mountain-View

Socials: - cal.com/gavmor

---

Posts10
Comments496
View on HN

I've got an application for this. Will try and get some benchmarks in the next few weeks. We're definitely attempting to converge on a quality inference without wasting tokens/time.

For now, we're passing the first pass to the humans, and that's roughly 80 for 20, but to get the last 20 without blowing up our token spend? This might be the approach.

Thanks for the write up comment, btw.

A regular LLM acts as a "policy," mapping a current state to a specific action (states → actions). Their new LLM acts as a "world model," mapping a current state and a chosen action to a predicted future state ((states, actions) → subsequent states). Instead of deciding "what to do," its explicit objective is to predict the exact environment observation that will result from the interaction history and the agent's current action.

I assumed at first that it was trained on synthetic data, but they actually went and deployed real physical hosts and virtual machines (e.g. Ubuntu, macOS, and Android) and browsers. They ran agentic systems on these continuously and recorded the actual, real-world interactions.

So it's an LLM that infers next state, or outcome,as structured data e.g. literal HTML code, UI view hierarchies, or accessibility trees.

Almost nobody optimizes compiled assembly code.

Compiled assembly code is not an input to the next compilation; source code is an input to the LLM's next inference.

Sure, maybe "prompts are the code," but you must realize that code is also the prompt.

Riding horseback saves time over walking but it's harder to smell the roses along the way. Nevertheless, millions now ride horses recreationally.

He was the perfect protagonist for a teenage boy: a coward, an underachiever, technically a wizard but only on a technicality, and frequently the most powerful spell in the universe was lodged in his head against his will. This will be familiar to anyone who has been sixteen.

s/frequently/initially

Also, how is a cowardly underachiever "the perfect protagonist for a teenage boy"?

"technically a wizard but only on a technicality" is obviously redundant

And what part of any of this is supposed to be familiar?

It's just a strange essay.

The terminal is keystroke-driven. It's character-selectable. It's reliable in a way that the GUI is not. When I drop frames, I can still enter the commands to rescue myself with some assurance they'll be interpreted, eventually.

I agree, a REPL isn't Unixy in the streams of text kind of way... or is it?

Agent Skills 3 months ago

I'm notorious for taking poetic license with naming—that's how we end up with `class Escutcheon`, or variables `recto` and `verso` where applicable in eg PDF generation.

But as much pleasure as I derive from novelty and specificity, my colleagues have oft expressed perplexity—whereas the terms which LLMs produce hew closer to the manifold (by definition!) and raise fewer eyebrows.

So, it has its turn.

I'm easily pushing 20 commits a day, but I won't pretend to have reviewed it all, let alone carefully. What I did was design it all carefully.

But, for some projects, yes—I still do line-by-line code review with a colleague.

Then again, a lot of my efforts are explicit refactor aimed at reducing LOC and tidying the codebase with, eg DRY.

The few times I felt lazy and let an AI do a simple function for me, all hell broke loose.

This is confusing, because LLMs are more than capable of implementing "a simple function." How did you spec it out?