36 commits by ‘tridge and claude’
https://www.youtube.com/watch?v=V0EAo9jo-U4&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20260603-rsync-goes-ai-slop-breaks-your-backups - podcast
time: 7 min 34 sec
https://pivot-to-ai.com/2026/06/03/rsync-goes-ai-slop-breaks-your-backups/
36 commits by ‘tridge and claude’
https://www.youtube.com/watch?v=V0EAo9jo-U4&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20260603-rsync-goes-ai-slop-breaks-your-backups - podcast
time: 7 min 34 sec
27 Comments
WhoIzDisIz@lemmy.today · 38 pts · 108d
You heard it from the Ray-Guns first, but apparently you need to hear it again: "Just say no!"
Kirk@startrek.website · -2 pts · 108d
blakestacey@awful.systems · 9 pts · 108d
The truly fundamental aspect of the entire philosophy, in practice, was telling people "Just fork it, then."
MoonMelon@lemmy.ml · 17 pts · 108d
Reading his response, I think calling it "slop" isn't being totally fair, but it does sound like he should hand it off again or close the project. Not having test coverage for something is bad, but it happens. It sounds like the alternatives have this issue also. But the sailing comment is kind of tragic. Just go sailing, dude. Unless you have a phylactery under your desk the project will outlive you anyway, and honestly that's the best compliment a developer can get.
dgerard@awful.systems · 11 pts · 108d
It literally is slop. It's always correct to call slop slop.
MoonMelon@lemmy.ml · 21 pts · 108d
If what he claims is true then he's using LLMs for test coverage with significant editing by hand. I hate LLMs, but even I have to admit this seems like one of the few, valid use cases of LLM assisted coding. Unless "slop" has become one of those words that's just lost all meaning.
dgerard@awful.systems · 18 pts · 108d
I commend to you jonny's thread on the tests:
https://neuromatch.social/@jonny/116666900898570791
It keeps turning out that when you look at the AI output, it's shit.
MoonMelon@lemmy.ml · 16 pts · 108d
I don't know anything about rsync aside from as a user, but I am pretty experienced with Python and I admit those tests look really bizarre. If he did "slot machine" code it (a term I wasn't familiar with) then yeah, I agree that's slop. If he didn't, I don't understand why he made these changes. OK yeah, that's a bad sign.
dgerard@awful.systems · 25 pts · 108d
every vibe coder insists they're shooting up krokodil responsibly
arbitraryidentifier@awful.systems · 8 pts · 107d
krokodil is such a good analogy goddamn
AnarchistArtificer@slrpnk.net · 12 pts · 107d
On one of the BlueSky threads going over over the test code, one of the things they uncovered was some stuff running as root which in no world should be necessary. He may not have just prompted Claude to "convert test suite to python", but there's a lot there that seem like clear red flags in terms of AI slop code.
Which is no surprise, really, given that properly proof-reading AI code is often much more labour intensive than just writing the code oneself. It's easy for things like this to slip through the cracks, even if you are trying to check the AI output
diz@awful.systems · 11 pts · 107d
It's a perfect example of how "using LLMs for test coverage" can also be harmful. He expected the tests to to prevent introduction of said regressions, probably based on a combination of the quantity of tests and their style (they look like what decent human written tests look like). But the tests are AI slop, and so they give a lot less value per line of code than he expects, hence a significant regression.
It is literally useful to call these tests AI slop, and the problem is in part caused by not calling them AI slop, and having consequent inflated expectations. LLMs are not any better at writing tests than at writing other code! It is merely that the bar for tests can, legitimately, be a lot lower (in projects where there would otherwise be no tests at all). Making an exception to calling AI generated tests "slop" is thus counter productive, because it leads people to act as if LLMs are actually better at writing tests than at writing other code, and not just because the bar for tests is frequently very low.
edit: actually scratch that I looked at the PR and those tests even look like dogshit and worse than the tests I seen claude write at a workplace that was into vibecoding (which i since quit).
degenerate_neutron_matter@fedia.io · 15 pts · 107d
gerikson@awful.systems · 7 pts · 106d
someone with a pretty website and a wife who knows statistics mounts an impassioned defence of tridge and the clankers:
https://alexispurslane.github.io/rsync-analysis/
mawhrin@awful.systems · 9 pts · 106d
a person whose last two years worth of github contributions are related to confabulation machinery, surely this is an unbiased analysis.
ebu@awful.systems · 8 pts · 106d
dividing by commits is some nasty sleight of hand given the commit rate has gone through the roof. "only 3 bugs per 10 commits!!" doesn't really mean much when there's an order of magnitude more slop commits than not
TinyTimmyTokyo@awful.systems · 8 pts · 106d
One of the most egregious examples of p-hacking I've ever seen.
captain_aggravated@sh.itjust.works · 2 pts · 107d
Suppose it's a good thing I switched to Borg-based backups.
mawhrin@awful.systems · 7 pts · 107d
so there's this thing with borg…
captain_aggravated@sh.itjust.works · 6 pts · 107d
What is it built on rsync?
dgerard@awful.systems · 6 pts · 106d
they too slurp at the slop sewer
Kirk@startrek.website · -5 pts · 108d
Feyd@programming.dev · 21 pts · 108d
"Not maintaining" would be better than what happened.
OwOarchist@pawb.social · 9 pts · 107d
Yep. Better to have no updates than to have broken updates.
Kirk@startrek.website · -2 pts · 108d
blakestacey@awful.systems · 12 pts · 108d
Honestly, I almost brought the banhammer down for this. Making excuses for shitty programmer behavior is bad. Doing it by pretending they're like victims of domestic abuse is worse.
blakestacey@awful.systems · 16 pts · 108d
"When help never arrived, he actively chose to make everyone else's life worse."
As Yoda would say, a fucking river cry me.
Kirk@startrek.website · -1 pts · 108d
V0ldek@awful.systems · 11 pts · 107d
I absolutely do get to call everyone who uses LLMs chuds, I actually do it all the time, it's a great past time that keeps me healthy and moisturised.
blakestacey@awful.systems · 10 pts · 108d
And you don't get to complain about me spending my free time banning you. Bye!
dgerard@awful.systems · 10 pts · 108d
wow that guy really went for it huh
V0ldek@awful.systems · 12 pts · 107d
No one is shaming him for not maintaining the project, we are, correctly and righteously, shaming him for using the Torment Nexus