- cross-posted to:
- kazkassukompais@group.lt
- cross-posted to:
- kazkassukompais@group.lt
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
But the answer to finding yourself being load-bearing is not to start using AI code with AI tests.
The Great Man theory of open source development, where it all hinges on one heroic individual, has always been a fatal weakness. It happens because the companies benefiting from the software just will not pay the individual guys who let their company work. So the companies try to make the guys feel obligated to do work for them for free.
Those guys have to start saying “no.” Go sailing. Declare the project closed and see if the beneficiaries will finally contribute. Maybe they will, maybe they won’t. But no company will put in the developers or money for this stuff to be done until you say “no”.
You heard it from the Ray-Guns first, but apparently you need to hear it again: “Just say no!”
Removed by mod
The truly fundamental aspect of the entire philosophy, in practice, was telling people “Just fork it, then.”
So that’s why my backup script, which has worked perfectly for months, failed completely the last time I tried to run it. Guess I’ll be downgrading to the last non-slop version.
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.
It literally is slop. It’s always correct to call slop slop.
I rewrote the rsync test suite in python from the old shell script design. I did the design for that myself (and I’m really quite pleased with it), but used claude with cross-checks from codex and gemini to do the grunt work. I did not just vibe-code “convert test suite to python”… I used AI tools to do the grunt work because they are good at that. I reviewed every part of it myself and ran through a huge amount of CI time getting it right
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.
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).
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.
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.
every vibe coder insists they’re shooting up krokodil responsibly
krokodil is such a good analogy goddamn
Suppose it’s a good thing I switched to Borg-based backups.
so there’s this thing with borg…
What is it built on rsync?
Removed by mod
No one is shaming him for not maintaining the project, we are, correctly and righteously, shaming him for using the Torment Nexus
“Not maintaining” would be better than what happened.
Yep. Better to have no updates than to have broken updates.
Removed by mod
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.
“When help never arrived, he actively chose to make everyone else’s life worse.”
As Yoda would say, a fucking river cry me.
Removed by mod
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.
And you don’t get to complain about me spending my free time banning you. Bye!
wow that guy really went for it huh








