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
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
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.