3uler

Idk I’m starting to have have trouble with the frontier models and a couple how to write like a human skills…

Calling per token usage of the US closed source labs has always been funny to me, we have a clear model of what it actually costs to host these models from open models.

Your subscription is not subsidised, it is just closer to the actual cost of the model…

Half decade? Its been getting worse for as long as I’ve been conscious.

I feel like a lot of the trade-offs forced on you by dsql, you are forced into when scaling Postgres.

Like if I’m an SRE/DBA and you running massive update queries in a single transaction, that is the first thing I’m getting rid of.

> industrial scale distillation attacks

You mean the industrial scale distillation attack you perform on the entire corpus of human knowledge… idk, call me cynical but you reap what you sow.

American dates are sooo fucking annoying…

idk, I'm of the opinion that you own the code you wrote with AI.

Markdown instructions are useful as durable context, but they do not replace programming. Their job is to keep intent out of a transient chat so both the developer and agent can revisit it. The actual constraints still belong in code: types, tests, linters, and dependency rules. Natural language can explain why a boundary matters; executable checks determine whether a change respects it. That feels more like a persistent layer around the programming workflow than a new programming language.

I agree. I keep agent memory off. In my experience, it remembers the wrong details and applies them in the wrong places. Project context should live in the repo, where the whole team can find it, review it, and correct it.

It should be treated as an explicit artefact of the codebase for Humans and Agents to work with.

I’ve never felt comfortable with how people use Claude Code or Codex as synonyms for Harness. It’s not wrong, it just reduces the harness to the least interesting part: the runtime. It’s the part you have the least control over. Most of us use what ever subscription makes most sense or whatever our company has settled on.

To me the interesting part of the harness is what you add on top, Brigitte Böckeler calls it the outer harness. I prefer the term Your Harness, your harness breaks down into two things: Skills and Loops.

Skills change what the agent knows and the loop changes how it works and checks itself. Both can mostly be encoded in Agent Skills

Your Harness should mostly agnostic to the agent you use.

In my experience, having worked at several large PSPs, it is Mastercard and Visa who are the morality police. Stripe are just enforcing the rules insisted on by them, and PayPal forgot about them 3 layoffs ago.

For me quickly scanning over the article, the fact that floating points were even presented as a possibility was an immediate red flag. And I pretty much stopped taking the rest of it seriously.