Skip to content
AI ConnectPowered by VELENTIS
AI-generated2 min

Rejecting Model-Generated Waste: Developers Launch the 'No AI Slop Manifesto'

At the AI Engineer Code Summit, engineers unveiled a manifesto against AI slop, demanding accountability, careful curation, and critical thinking over unreviewed model output.

This article was AI-generated and published automatically. Context, labelling and all sources at the end of the article.

(KI-generiertes Symbolbild: Gemini / AI Connect)

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.

What this means for you

The manifesto marks the end of uncritical enthusiasm for automated volume and signals a renewed commitment to craftsmanship and diligence. For software engineers and creative professionals, submitting unverified machine output is increasingly viewed as a standard of poor quality and unprofessional conduct. Moving forward, the true competitive advantage will belong to those who exercise rigorous editorial judgment over their tools.

Perspectives

Coverage: 3× Other

One story, several angles: how each source frames the topic, each with a verbatim quote.

  • latent.spaceOther

    The publication presents the manifesto as an initiative arising from conference discussions that is intended to serve as a useful tool for workplace conversations.

    Original quote

    „We started this manifesto to offer a useful tool for discussion at work, and hope it gets used that way.“

    latent.space
  • news.ycombinator.comOther

    The platform captures the manifesto through a community debate where developers discuss the definition of AI slop and how to handle AI-generated code.

    Original quote

    „Slop is when we put less effort into producing something than we ask the consumer to spend understanding it.“

    news.ycombinator.com

Source classification is maintained editorially (political spectrum only where consensus is broad; vendor communication is PR, not journalism). Unlabelled sources are unclassified: we do not guess.

Evidence

Solidly sourced
67/100
  • On November 13 and 14, 2026, speakers and attendees of the AI Engineer Code Summit launched the 'No AI Slop Manifesto'.

    verified
  • Dex Horthy introduced the manifesto during the closing keynote, co-signed by tech figures including Kent C. Dodds and Philip Kiely.

    single source
  • The manifesto reached the top spot on Hacker News shortly after its public presentation.

    single source
  • The core principles of the manifesto include 'Outcomes over output' and 'Our own thinking over a model's first draft'.

    single source

The evidence score is computed, not hand-set: from confidence, the number of sources and the share of verified statements.

Source & transparency

As of: November 16, 2026

AI-generatedAI-generated: produced automatically from vetted sources with technical quality checks (source, quote and figure verification); no human sign-off of each item before publication

Sources
3
Verified statements
1 / 4
Evidence score
67Solidly sourced

Want to put this into practice?

We connect you with suitable AI providers from the DACH region, free of charge and without obligation.

What's next?