Yeah for sure and that’s great and all but I think what they were really asking is how they’ll feed their kids

And that's really my issue, for example when you define "has no trailing whitespace", you are basically writing a piece of the implementation. Cover all behaviors, and you have basically re-implemented the function, no?

In other words, if I have the full formal spec of f(), isn't that the same thing as having f()?

I guess doing things twice can help catch errors, but I fail to see what’s so special about formal specs if they can suffer from the exact same bugs as the tests/implementation.

I guess the root of the problem is if you want to formally prove that a program does something, you have to be very specific (heh) about what that something is, at which point you are basically just writing tests/implementation all over again.

I have been looking into this on and off for years now, and I keep feeling like I’m missing something, but I don’t know what it is.

Can anyone enlighten me?

You would be surprised what normies are willing to delegate to AI.

Who makes consumer devices? Google

Who makes operating systems? Google

Who makes browsers? Google

Who makes the world’s most popular websites? Google

By the time 90% of average internet users get to chatgpt.com or whatever, they already went through several Google chokepoints, each layer is one more place Google can answer their questions.

And that’s not even getting into the chips, the data centers, the data, the talent, the consumer apps, the enterprise apps, the cloud platform, the brand, and of course the biggest cash printing machine in human history.

You would honestly have to be insane to bet against G.

Unfortunately, companies often measure developers by their own PRs.

An unfortunate outcome of this is that writing docs for other developers isn’t really incentivized properly (and with stack ranking, you might even say it’s disincentivized). Writing docs for Claude, however…

NFTs use the same machinery but the premise is that you own something else, e.g. an image (or real estate!) but nothing on-chain actually grants that ownership. To the extent real ownership exists at all, it lives entirely off-chain, e.g. in a legal contract (that would hold with or without the blockchain).

I am not a fan of crypto either way but NFTs are just ridiculous.

Any person with common sense and basic technical understanding could tell you NFTs were an incredibly dumb and useless idea from the very start. All you “own” is an entry on some ledger, which doesn’t inherently give you ownership over anything else.

So, is this like a skill the LLM should follow, or an actual "workflow" in the deterministic sense?

If it's the former, is it even reliable for long running tasks? If it's the latter, can users interact with it?

Also, this is very scummy.