jj4211

joined 3 years ago
[–] jj4211@lemmy.world 1 points 9 hours ago (1 children)

If someone buys a synthesizer from a store, no one is writing an article on how neat it is that they bought a synthesizer.

[–] jj4211@lemmy.world 4 points 17 hours ago

I didn't say folding, it was literally bragging that they could get it to just get clothes off a bed and into a basket

[–] jj4211@lemmy.world 15 points 19 hours ago (2 children)

They can barely get a robot to slowly pick up clothes in a controlled, small environment.

They have been having a very hard time with physical world stuff. They've mostly been making them do stunts like dancing and running with the occasional tele operated demo and supremely basic things like the picking up clothes thing.

They don't have the volume or quality of training data to pull the same stuff they have pulled off in pure digital terms. Quite critically they cannot capture tactile part of human work, and that causes a great deal of limitation.

[–] jj4211@lemmy.world 19 points 20 hours ago

Yeah, the FAA incident may or may not be related, but it certainly seems just like an averted disaster at my workplace where someone proposed a Claude translated network config to go from one vendor to another and I had to manually interject and insist on a review and found that claude completely screwed up something that would have done... well pretty much exactly what happened to the FAA, had it been actually applied.

The banking issue they flat out mentioned it was AI related, but they only explicitly admitted it was trying to remedy an AI detected security issue. Question is whether they took the AI suggested remediation and got screwed by it, or if a human boffed the remediation, and it's tough to say without the bank coming out and being explicit about it.

Microsoft came out kind of vague and said some change was made to Windows OS in July that caused the catastrophe that they had to unwind. Again light on detail, but given their excessive public bullishness on full on agentic AI and the sort of change described, it's almost certainly a vibed change in pursuit of what would likely be considered a premature optimization. Huge risk, no reward sort of change for the sake of someone's AI KPIs, probably.

A bit grumpy because in my work, I try to be as hard on the AI skepticism as my company will take, and onboarded a pretty all-in AI coder and thought I had at least gotten them to actually make sure their change at least specifically did as they intended, and not merely passed the automated test suites. I sat with him interactively on some pull requests to make sure he actually made a plan to try out his changes and validate the behavior with his own eyes, and thought I instilled a good habit. So shocker as the first 'big test' after I trusted that he actually vetted some of his changes fell over. His pull request even explicitly listed the scenarios and claimed that each one was tried. He then had to admit that Claude just made up that it tested the scenarios tested but he figured it was a safe bet if Claude 'audited' it that it was ok if it lied about actually trying the scenario...

[–] jj4211@lemmy.world 17 points 1 day ago* (last edited 1 day ago) (1 children)

Weird flex but ok.

[–] jj4211@lemmy.world 6 points 2 days ago (1 children)

A fair point but we called super simple scripted NPC behaviors "AI" and no one batted an eye...

[–] jj4211@lemmy.world 13 points 2 days ago

The thing is that AI itself is not as directly obnoxious, but it has made obnoxious people extra obnoxious. What was the cesspool of YouTube comments became the video feed. Everyone who minimized everyone else's contributions got to show exactly how little they regarded others by trying to replace them with AI.

AI makes assholes more prominent in our lives.

[–] jj4211@lemmy.world 5 points 2 days ago

Stephen King liked the ending better than his own.

[–] jj4211@lemmy.world 1 points 3 days ago

Yeah, the things is the processes at work are all driven by optimism, "won't fix" is not an available option for a bug, and "not bothering" isn't a valid answer to a PR. And both the owner and reporter must agree on any closure.

So we end up with perma-issues that can't be closed.

I can effectively block the PR, but so long as the submitter wants it open... Doesn't matter how senior I am.

[–] jj4211@lemmy.world 1 points 3 days ago

In TOS, they had the 'Euginics Wars' as a plausible WW3, but did not explicitly name it, but that would have been the 90s.

But other than that, the year asserted in First Contact is.... oh no...

[–] jj4211@lemmy.world 1 points 4 days ago* (last edited 4 days ago) (2 children)

Just so long as your ultimate pull request is plausibly human viable.

Have been fighting someone because they submitted a 15,000 line pull request for 'one' feature and no one is going to review that mess. I gave a very quick 'for example' showing in the first 30 lines of changes that it's screwing around with stuff that has nothing to do with what the sloperator said they pointed out.

Now they are complaining that I won't take code even though Claude audited it and said it is all good...

(This is work, so I don't have the luxury of just permanently ignoring them).

[–] jj4211@lemmy.world 1 points 4 days ago

It's bad enough in commercial software land where I regularly hit issues because multiple vendors did the same thing in incompatible ways.

Now slop encourages people to never try to get on the same page.

view more: next ›