The No AI Slop Manifesto argues that AI is a powerful tool, but its ability to generate large volumes of work can overwhelm the human attention needed to understand and review it. It defines “slop” not simply as AI-generated material, but as work passed along with too little care for its quality or for the effort readers must spend making sense of it. The problem is asymmetric: producing a huge code change or lengthy document is becoming cheap, while reviewing it remains costly. Slop also accumulates in code, messages, and organizational knowledge, where later work can repeat its mistakes. Pressure to increase output and a bias toward adding rather than fixing contribute to the problem.
The manifesto calls for prioritizing outcomes, understanding, and good work over speed, volume, or convenience. People remain responsible for the intent and consequences of what they ship, should disclose AI assistance when relevant, and should examine important parts of generated work. Review should match the stakes; automated checks help, but do not replace human judgment. The goal is not to reject practices such as one-shot prompting or vibe coding, but to use them when they serve a useful product, maintainable systems, or save people time. When errors recur, teams should improve tools and guardrails rather than repeatedly patching outputs. Its central principle is to use AI to improve results, while treating human attention and understanding as valuable resources.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.