Comment Re:Al promises to be good (Score 1) 35
Ok, now someone has to be called AI Capone.
Ok, now someone has to be called AI Capone.
Well the FAA thing, at least if they are being truthful, sounds something like either a BGP screwup or a broadcast storm (we only get the answer after the telephone game through politicians). Which doesn't rule out AI bullshittery (they could have asked Claude for a good router config and taken it at face value, I know one person who did do that and sent it to a technician and I was able to interject because it did explicitly connect broadcast domains that were supposed to be distinct).
Microsoft and banking are squarely in the realm where AI codegen is likely a component.
In terms of what to look for, for the bullish AI management, it's damn near impossible. Someone submitted a pull request of thousands of lines of code ostensibly for a very minor change. Management is questioning the decision to block it because it's too big to plausibly review and that much change is extremely bad smell for the goal. However 'Claude audited it' so it *should* be good, and are we just being luddites? In my case, we still win in practice by rejecting it, but from public reporting it sounds like some other organizations may not be so fortunate.
Sounds like the excess toxicity was the original failure, not a consequence.
The expected behavior that failed is actually letting people know to get out of the water.
It's not really the automation that's the problem, it's the lack of follow through.
Good, it's automatically monitoring the chemicals. Bad, it doesn't actually do anything about it except send an email.
If it was fully closed loop automation complete with clear and audible local alarm, then that would have been great. Though one could say it should still be backed up by a human doing a periodic manual check, just like my local cheap pool does every 30 minutes or so.
This is really "Bad design leads to chlorine gas poisining".
You have a local monitoring solution that *doesn't* sound an audible alarm, but just expects an email notification to drive? What the hell are they thinking, especially with a health and safety implication.
Certainly is a creepy level of hero worship that I find offputting.
But I can understand trepidation over transitioning from a leader who was a founder, there before anyone would have had any reason other than actually wanting the mission to work out to be interested. To a scenario where whichever shark makes it through the frenzy to head the second largest company in the world... The sorts of people that manage to get in charge of big money businesses generally are not the sort of folks interested in the actual mission...
Note that this all is around the Compaq BIOS case, and a part that keeps getting glossed over is the finding that the part being protected, the ABI interface, was not substantial enough for protection.
Software that is more substantial beyond just ABI/API is likely to be considered differently.
Note if it documents the full code body and translates that back into code, that may be treated differently. The BIOS documentation covering inputs and outputs, but not how those things are processed are one thing, but if it is a full prose description of the execution steps of a function, well that's different. In short, the LLM is likely to carry over the substance of the implementation in the prose, and break the whole promise of 'clean room'.
While true, mixing up 'reign' and 'rein' is a pretty non-LLM move. We see the words as very similar, but token wise they don't have anything to do with each other, though maybe muddied by copying human mistakes.
In the man page I see:
RETURN VALUE
On success, a pointer to the hashed password is returned. On
error, NULL is returned.
Yeah, crypt() *should* return a NULL pointer, *not* some arbitrary string when there's a fault. Entirely musl's bug.
I would hardly call profit taking when a big gain is *guaranteed* a "moron" move.
At some point it really will be the top of the market.
Besides, it's less about performance and more about investor sentiment. You are predicting the other humans level of investment, *not* the financial health of the company, unless you are in it for the dividends of course, but relatively fewer people are thinking dividends. The market value of those projections are already baked into the price today.
But even by the standard of financial results, the projections are subject to change. If some of the neoclouds fold up, then the projections evaporate.
On the ATM card, it's about cost reduction.
On the PC side, it is, fundamentally, a platform that emphasizes flexibility versus mobile that screws flexibility while locking down. So it's mainly about how far a malware could get running against the wishes of the device operator, rather than what a user could do to misbehave. I'm not taking the trade-off, but there is at least a rationale.
More to the point, for them to have the authority to even theoretically facilitate such volumes of transfer, regardless of software compromises...
Given the way big publishers have already made games a cesspool of microtransactions, online-only operation even for single player experience.... Retro game interest is *long* overdue.
AI slop is merely the latest 'slop' in an industry long rotting.
I'm waiting for Super Intelligence II Turbo: Hyper Fighting Championship Edition.
You know that feeling when you're leaning back on a stool and it starts to tip over? Well, that's how I feel all the time. -- Steven Wright