The most frustrating failure mode right now is that people submit issues that are not in their own voice. They contain an observed problem somewhere, but it has been thrown into a clanker and the clanker reworded it and made a huge mess of it. Typically, it was prompted so badly that the conclusions produced are more often than not inaccurate but always full of confidence. The result is complete guesswork on root causes, fake-minimal repros, suggested implementation strategies, analogies to adjacent but often the wrong code, and long lists of error classes that might or might not matter. [...]
So at least personally, I increasingly want issue reports to be condensed to what the human actually observed:
- I ran this command.
- I expected this to happen.
- This happened instead.
- Here is the exact error or log.
— [Armin Ronacher](https://lucumr.pocoo.org/2026/5/24/pi-oss/), on slop issues filed against [Pi](https://pi.dev/)
Tags: [ai](https://simonwillison.net/tags/ai), [github-issues](https://simonwillison.net/tags/github-issues), [llms](https://simonwillison.net/tags/llms), [ai-ethics](https://simonwillison.net/tags/ai-ethics), [open-source](https://simonwillison.net/tags/open-source), [coding-agents](https://simonwillison.net/tags/coding-agents), [generative-ai](https://simonwillison.net/tags/generative-ai), [armin-ronacher](https://simonwillison.net/tags/armin-ronacher), [pi](https://simonwillison.net/tags/pi), [slop](https://simonwillison.net/tags/slop)
source & further reading
simonwillison.net — original article
datasette-agent 0.1a4
FTC to Require Cox Media Group, Two Other Firms to Pay Nearly $1 Million to Settle Charges They Deceived Customers About “Active Listening” AI-Powered Marketing Service
Datasette Agent