manmal

How can IgE get bored? That doesn’t sound right. Why would the body, a master of efficiency, produce IgE just for fun?

But good gherkin tests encode pretty well what I’m trying to achieve, because they can be super high level - any flight level I want them to be. The only precondition is that the test env can deterministically measure the conditions.

Given the user is logged in

And the XYZ endpoint is offline

And the dashboard is visible

When the user clicks on the endpoint status

Then an overview of XYZ endpoint errors is shown

I see how this could be useful, to roast agents while they are debugging or building something.

Why not use gherkin given/when/then stories, and build E2E runners and maybe also unit tests for them? I don’t understand why a new spec format is necessary, which forever binds you to using agents for evaluation. Deterministic tests also have the advantage that they are harder to cheat on. If they are green, they give me a strong signal I can trust.

Yes it’s basically unlivable. It’s super small and way too many people want in, every day. It’s also a very beautiful spot and I sometimes crave going to that wider area (Salzkammergut).

Salzburg is only 70km from Halstatt, but interestingly that name comes from nearby Reichenhall (Germany), another big salt producer.

Sure but that’s probably 100x max? It won’t magically work, there’s a lot of (auto) review and verification that has to be carefully setup, so things actually work in the way you need them to. I’ve done it, it takes days until it’s good.

Certainly not for infrastructure.

Isn’t the Muse team just 200 people? I guess you don’t need that much work done.

Except for platform constraints, like needing to use JS or Swift/Kotlin, why would I use anything else than Rust? I can’t even properly read it, but the agents somehow make it work well and the code doesn’t look particularly cluttered; and it’s so fast.

Isn’t input so much cheaper because it’s just less work? Prefill is usually 10-20x as fast as generation.

If you have 200k context, but only 200t/s prefill, then you’ll wait multiple minutes when continuing an average session from yesterday. Or compaction - might take 15 minutes.

It’s this year’s most memed trailer. It’s also where the wide eyed Elizabeth meme comes from.

Not even hopping. Just tilt/lift the car through the tight spot.

> the removal of all human leverage via their labor

I’m not convinced at all that SI will ever be able to produce the correct result with little input. The advancements in capability I’ve seen in models is that they understand my intention better, and follow industry best practices better, so their output is often acceptable. But I absolutely have to make my intentions known, as detailed as possible, or I will get the mediocre, standard solution that falls out of the weights.

I’ve been having trouble with models always steering towards certain solutions - they insert a queue here, a mutex there, a backoff over there. If I remove those, and let the model freely rebase the PR stack, then it will re-insert those mechanisms because it has been specifically trained to do exactly that. It’s essentially boilerplate, smoothly aligning my codebase to match their weights. Which is often good enough! They are training the models well. But individual problems require individual solutions.

My personal take on the human part in all this is: We get to decide, and the models obey. Our decisions are now super leveraged. So let’s make good decisions, and communicate them well. The layer of where decisions yield the most leverage, has been pushed upwards (I see it on the type and function signature level, others will see it even higher), but IMO it won’t be possible to push it up much further without losing truth to the decisions we need to make for a good product.

It’s just that the vibe coded stuff has so many assumptions baked in, that you will be constantly surprised about the behaviors your slopped codebase has. Doesn’t matter for small tools, where you’ll be delighted that clicking that one label copies it to your clipboard - nice one, Claude, that’s delightful!

It’s less nice when your web app launches that other service only when the other Tailscale node is up, because the agent interpreted your prompt as a hard access rule.