3,473 karma · joined March 18, 2021
I don’t see that changing, to be honest, but it’s interesting that this never even occurred to me. It seems so obvious in hindsight. Quite the blindspot.
Something about the SO incentive system created the most hostile platform imaginable.
This is overselling it. In all implementations of this that I’ve seen, a more correct phrasing is “won’t stop until it pinky-promises it achieved your goal”.
It usually relies on something like a hook that refuses to let the agent stop unless it includes a “promise sentinel”, which is basically the model having to include “I swear I’m done” in the response (usually as a Markdown comment so the user doesn’t see it). If that sentinel isn’t in the response, the hook rejects the completion and hands it back to the agent (sometimes it also restates the goal to keep it focused). It’s useful for sure, but it fails many times for obvious reasons.
More robust implementations use the hook to spawn another agent that verifies the goal is achieved, but that too isn’t prefect and sometimes performs worse.
Of course if you have a problem that can be deterministically verified, you could have the hook run this verification instead, but this is usually not the case (and even when it is, agents will often cheat the verification e.g. by deleting a test file).
I think it’s the disconnect. Each persona is an expert in their own field but is completely oblivious to other critical areas.
The founder knows how to raise money but doesn’t really understand the customers. The engineer knows the tech but doesn’t really understand what it takes to keep the business afloat. The salesperson knows what customers want but doesn’t really understand what’s possible to make. The investor knows the numbers but doesn’t really understand how poorly the business is run.
I suspect if you look at successful startups you’ll often see a very small (1-3) group of founders who are very close, each can do more than one thing really well, and their combined expertise means that together they have very few blindspots.
But then what if we end up with ASI that can comprehend and make it useful for us?
Even if I write down every single thing it did wrong and how I’d do it, and even if I turn those into rules, it will know how to follow these specific rules, but for some reason it can’t seem to generalize beyond that. And the real list of rules seem truly infinite.
(If the argument is that subsidizing books helps the poor, I’m all for it, a nonprofit or a charity would be a much better framework)
This is the public sector M.O, instead of admitting something is obsolete they grab more scope and funding.
My local post office now sells iPhones. And why shouldn’t they? Nobody stopped them when they just sold SIM cards, and then cases and chargers. It’s like a law of nature.
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.
It’s beyond me how these super important (and controversial) people keep diaries where they lay out their evil plots like a villain from Scooby Doo. And save it on a work computer.