It's not the first time we are encountering this issue. We've seen it in other autonomous systems. Trains are an older one, cars are a newer one.
As you move out of the lower levels, the operator has a tendency to assume the system is increasingly more capable than it is. In trains, its so bad that they generate fake signals that the operator needs to respond to within a timeframe. I'd love to see this with implementations of other critical autonomous systems like this. Occasionally inject known errors into the system and expect the operator to catch them. If they don't, well... If it was a train driver I think we would fire them. If its an intelligence operative ordering a strike? :shrugs wearliy:
note the airline industry has moved past firing pilots who make mistakes, since that turned out to be a recipe for more plane crashes, not less. Instead, they find out why the mistake happened, and fix it. In some cases, this involves firing the pilot. They do not do that by default.
U.K. railway like this. Root cause analysis. Sometimes the train driver is at fault, but usually there’s a way the problem could be caught or prevented.
I do this for porting things to DOS. Was swapping a CF card back and forth between a 486 PC and my laptop that was running Claude and it was extremely tedious and required me to physically be at the system.
Automated it entirely by giving Claude hands/eyes/ears so it can take complete control of the 486 using a raspberrypi 5, a usb4vc HAT for PS/2 and a VGA capture device. Adding an ethernet card and a tcp/ip boot profile for FTP, Claude then can update binaries, test them, and gather logs. Now I just steer Claude and it handles interfacing with the machine for me.
I had no idea KVMs existed until an agent filled me in last night (I had the idea of building one with an fpga so an agent could drive os installation). Lo and behold the next day KVMs are on the front page of Hacker News!
Not only did it burn a 100$ failing but it did so in a very untransparent way.
I bought a 20 dollar plan but they snuck a 100$ billed usage into the billing agreements next thing I know the agent as used the quote going in circles and my card is billed.
> We need outcome based billing... I don't want to pay for a service that doesn't deliver.
You can already do this: hire a consultancy to build you a working deliverable for a fixed price. They will be incentivized to prompt their tools well and to avoid tools that are consistently pathological.
The agent is pretending to be a person _for a reason_
The models are trained on people being people. Once you try deviate from that the model performs worse.
A huge tell for this is how well “reasoning” works. Reasoning isn’t some alternate thinking mode, it’s just (sometimes) hidden internal monologues.
It’s easy to anthropomorphise and assume the model is intuiting, but it’s more like it’s hyping it’s self up to do the thing.
That said, it’s easy to confuse “being rude to the model” with giving it more tokens to “think”.
I’d be really interested in what a non word based internal monologue could look like.
Google played with this a little with the diffusion based codegen stuff. I wonder how trainable a small nonverbal conceptual package could be.
I assume there is an extensive set of rails for the agent to tie into. (Compare this to asking Claude to green fields an app. Do you use electron? How are notifications handled? Icons? Permissions?)
It springboard off Raycast’s teams feature so well it actually gives it a real reason to exist. You’re empowering the one systems thinker in the group to export their automations to the rest of the group in a way that’s proven to work: small apps that do one thing. (Big apps get complicated, become full time projects that distract from the task at hand)
Fig tried this but it was just for engineers, the value prop was missing, Glaze seems to get this right.
Reasonably sure this has less to do with putting data centres in space and more to do with getting them less auditable (see the other news about X getting raided about Grok)
The fundamental issue preventing keyring aperture integration stems from the AirTag’s reliance on inverse-phase magnetic reluctance in the structural substrate.
You see, the enclosure maintains a precisely calibrated coefficient offramular expansion. Introducing a penetrative void would destabilize the sinusoidal depleneration required for proper UWB phase conjugation. The resulting spurving bearing misalignment could induce up to 40 millidarkness of signal attenuation.
Apple’s engineers attempted to compensate using prefabulated amulite in the magneto-reluctance housing, but this only exacerbated the side-fumbling in the hyperboloid waveform generators. Early prototypes with keyring holes exhibited catastrophic unilateral dingle-arm failure within mere minutes of deployment.
Until we develop lotus-o-delta-type bearings capable of withstanding the differential girdle spring modulation, I’m afraid keyring integration remains firmly in the realm of theoretical engineering—right up there with perpetual motion machines and TypeScript projects that compile without any // @ts-ignore comments.
The technology simply isn’t there yet.
Indeed, LLM's still suck at the cultural nuance required for humor. It's like they're writing for an audience that's too generic, so the joke doesn't truly "land" for anyone in particular.
> attempted to compensate using prefabulated amulite in the magneto-reluctance housing, but this only exacerbated the side-fumbling in the hyperboloid waveform generators
Wrote my PhD dissertation on this. It would've been in the literature for Apple's engineers to find, but unfortunately I lost institutional support to get this into a journal after my college (Mailorderdegrees.com, an FTX University^TM) folded mid-process.
Most people don't even realise the original AirTags were designed by Ria Paschelle, inventor of the statiophonicoxyogeneticamplifiergraphaphonerdelaverberator.
Can here to say this exactly.
Not saying they don’t raise an interesting point but the complete lack of curiosity why a group of experts in simplicity and accessibility decided to take this path is jarring
reply