andyhedges

With Y2K we fixed the issue, if a bunch of work hadn't had gone into that then there would have been wide scale impact. Critical systems were fixed hence no disaster, it wasn't people fussing about nothing.

Only if you have a Beowulf cluster of tiktoks

It's interesting, the "discernment horizon" as Yegge puts it: the point where humans can't verify an answer because checking it is harder than producing it.

I'm not sure it's quite that simple.

I have a couple of problems I can't solve myself, although variants have been solved by others, so we know they're human-solvable. Verifying a candidate solution, however, is relatively easy.

For example, I've repeatedly asked frontier models (including Fable) to produce a fast squaring routine for arbitrary precision integers that beats GWNUM running under Rosetta 2 on Apple Silicon. None have come remotely close to the best human-produced implementation. After hours of iteration, Fable's best attempt was still about 4x slower than the Rosetta-translated GWNUM, despite GWNUM not even running natively.

The point is that direct understanding isn't the only way to judge correctness. We often build tests, benchmarks, and oracles that let us validate artefacts produced by people or systems that are operating beyond our own cognitive abilities. Perhaps the real limit isn't a discernment horizon, but a horizon for constructing effective evaluators. Can we layer evaluators to get even more magnification; I'm betting we can.

For the LLM it's a probabilistic set of strings that achieves the outcome, the highest probability set didn't work, try the next one until success or threshold met. A human sees the implicit difference between the obvious thing not working indicating someone doesn't want you to do it, but an LLM unless guided doesn't seen that sub-text.

So chmod +x file didn't work, now try python -c "import os; os.chmod('file',744)"

It's when they sniff the glue, then things get wild.

Isn't the what sftp is? sftp multiplexes commands and data, and is single port without all the old fashioned two port negotiation of FTP.

Yes, I'm saying it's not a good analogy

> We require age minimums for driving, voting, and drinking because we believe maturity only comes through lived experience.

Not true, we do this because the 99% of the time it's true, however there are people who would be perfectly competent and responsible to drive without living to the age of 16-18. Same with voting, there are humans who have a deep understanding and intelligence about politics at a younger age than suffrage. Equally there are people who will be reckless drivers at 40 and vote on whim at 60.

We have these rules not because sophistication only comes through lived experience, we have them because it's strongly correlated and covers of most error cases.

To take this to AI, run the model enough times with a higher enough temperature, then perhaps it can solve your challenges with a high enough quality - just a thought.

Nuance!? This is The Internet, we can't be having any of that here.

I have it (claude, codex) summarise what we've discussed about a design, big change, put it in an MD file and then I correct it, have it re-read it and then do the change.

Then later if it goes off piste in another session tell it to re-read the ADDs for x, y and z.

If someone could make that process less clunky, that would be great. However it's very much not just funnel every turd uttered in the prompt onto a git branch and trying a chug the lot down every session.

Can't you just reset the password on account without the dot it in? Lock them out.

Couldn't you play a WAV too? But they were too massive at the time for most peoples bandwidth.

Yes, but the concept existed in 'process servers' 'EAI hubs' and various other names. EBS caught on as the defacto term later.

SOA is more than just RPC it's about the decomposition of your organisation in to cohesive (from a functional(ity) perspective) units of software, to reduce the need to make the remote calls, but more importantly allow you to organise your engineers into small enough groups of people to be effective (7 give or take one person).

ESB simply add more complexity in the middle that needs yet another team to manage.

SOA never required an ESB, this was simply vendors trying to shoehorn in a saleable unit of software - which they succeeded at better in the 90s. Likewise I've seen people implement microservices with an ESB in the middle.

Long an short of it is the ESB is an anti-pattern, always has been and SOA and microservices are the same thing.