On November 13 and 14, 2026, software engineers and industry practitioners gathered at the AI Engineer Code Summit to confront an escalating byproduct of the generative technology boom. During the conference's closing keynote, developer Dex Horthy publicly unveiled the 'No AI Slop Manifesto' to address the flood of low-quality automated output sweeping the industry. The declaration was co-signed by prominent tech figures including Kent C. Dodds and Philip Kiely, lending immediate professional weight to its central critique. Within hours of its introduction, the document resonated deeply across the global programming community and rapidly climbed to the top spot on Hacker News.
Taking direct structural inspiration from the landmark 2001 Agile Manifesto, the document establishes clear guiding values for working responsibly with modern artificial intelligence. At the core of the initiative is a precise definition of the term 'slop', which refers to unvetted, synthetic debris increasingly clogging codebases, communications, and digital platforms. The authors define slop as any content where the creator invested less effort in producing it than the recipient must spend reading, understanding, and validating it. This fundamental asymmetry shifts the cognitive burden away from the publisher and unfairly forces reviewers, maintainers, and colleagues to untangle poorly conceived, machine-generated artifacts.
To counter this degradation of digital work, the manifesto outlines explicit principles designed for engineers, creators, and technology teams. Key declarations include 'Outcomes over output' and 'Our own thinking over a model's first draft'. The text explicitly rejects the notion that churning out massive volumes of synthetic code or prose represents genuine productivity or technical advancement. Instead, developers are urged to treat raw model generations merely as unrefined starting points that demand rigorous intellectual scrutiny and personal verification before ever entering production environments.
The manifesto gained broader momentum through curation by the platform Latent Space, led by industry observers swyx and the AINews team, which sparked wider discussion well beyond conference attendees. In subsequent debates on Hacker News and across developer forums, practitioners voiced mounting frustration over the daily influx of unreviewed pull requests and auto-generated documentation. Engineering leaders pointed out that reviewing and debugging flawed synthetic contributions frequently takes far more time than writing clean logic from scratch. Consequently, the initial illusion of accelerated development has begun creating costly organizational bottlenecks and severe technical debt across engineering organizations.
Industry observers view the launch of the manifesto as a pivotal turning point in the evolution of generative software tooling. The broader conversation is shifting away from uncritical awe at automated synthesis and toward institutionalized editorial and technical accountability. For employers and technology leaders, the manifesto sends an unmistakable signal that unedited artificial intelligence outputs are increasingly seen as signs of negligence rather than indicators of efficiency. In the long run, the initiative seeks to establish a professional culture where human critical judgment, accountability, and careful curation remain the primary benchmarks of engineering excellence.

