<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc" -->

---
title: I Don’t Want to Interact With Stochastic Parrots | daily.dev
description: A personal manifesto rejecting all interaction with AI-generated content, arguing that chatbot text, images, and code are hollow, unmaintainable, and harmful...
canonical: https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: I Don’t Want to Interact With Stochastic Parrots | daily.dev
og:description: A personal manifesto rejecting all interaction with AI-generated content, arguing that chatbot text, images, and code are hollow, unmaintainable, and harmful...
og:url: https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc
og:image: https://api.daily.dev/og/posts/dDAbuzTwc.png
og:image:alt: I Don’t Want to Interact With Stochastic Parrots
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# I Don’t Want to Interact With Stochastic Parrots

**[Lobsters](https://daily.dev/sources/lobsters)** · 11 min read · 0 upvotes · 0 comments

## Summary

A personal manifesto rejecting all interaction with AI-generated content, arguing that chatbot text, images, and code are hollow, unmaintainable, and harmful to human thought and learning. The author refuses to read AI-written text, view AI-generated images, run AI-generated code in projects, or engage in conversations that cite chatbot output as evidence. Generated code is called uniquely dangerous because, unlike bad human code, nobody can explain why it exists, making codebases unmaintainable. As an educator, the author now requires students to submit only self-produced work, arguing chatbot use degrades learning and self-confidence, while conceding private, non-bragged personal use is nobody's business.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://ploum.net/2026-09-09-ai_policy.html>

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 86 comments across lobsters, hackernews (as of 2026-09-13).

**TL;DR:** Reactions split sharply: many push back on the manifesto as reductive, outdated, or reactionary given LLM progress, while a smaller but vocal group shares the author's frustration with AI slop and eroding engineering rigor.

**Sentiment:** 15% positive · 30% mixed · 55% skeptical

**The case for**

- Some feel strongly that outsourcing thinking or coding to LLMs erodes personal responsibility and codebase understanding.
- A few describe actively blocking or refusing to engage with anything that smells like AI-generated content, citing attention and quality concerns.
- One commenter argues moral/aesthetic objections to LLMs can stand independently of whether the technology 'works' technically.

**The pushback**

- Many argue the 'stochastic parrot' framing is outdated given recent LLM capabilities like solving hard math problems.
- Several say humans are just as capable of producing average, formulaic content, undercutting the human/AI quality distinction.
- Some see the anti-AI stance as performative rebellion or false purity rather than a substantive critique.
- One long rebuttal argues there's no evidence LLM-assisted projects show any measurable quality regression versus pre-existing trends.
- A commenter notes that refusing AI-assisted PR reviews may lead to shipping less secure software by ignoring useful catches.

**By community**

- lobsters (mixed): Discussion drifted into a long philosophical tangent on free will and stochastic parrots, alongside a substantive technical debate over whether LLM-written code will degrade codebases long-term.
- hackernews (heated): Sharp disagreement between people defending the anti-AI stance as principled and others dismissing it as luddite, outdated, or performative, with side-arguments about moderation and downvoting.

**Hottest debate:** Whether AI-generated code inherently degrades codebase quality and maintainability over time, or whether that fear is unfounded/no different from existing human-written cruft.

**Open questions**

- Will projects that heavily adopt LLM-generated code show measurable quality or security regressions over the coming decades?
- Is the 'stochastic parrot' framing still accurate given more recent LLM capabilities?
- Where exactly should the line be drawn between acceptable personal AI use and harmful reliance on it?

**Highlights**

> > I’m convinced that accepting generated code will lead most projects to become broken beyond all hope of repair in only a few years. "Carefully reviewing" will soon not be enough. Unfathomable code will eventually slip in and gradually destroy the whole project. I predict that the projects too important to be left to rot and die will take decades to recover from those couple years of "assisted productivity." I always appreciate when people make concrete predictions. I'll take the other side of this one: I expect the use of LLMs in, e.g., Linux, Chrome, Firefox, node.js, z3 etc will increase over the next decades, and that if you could somehow assess the quality of these projects over time you would not notice a negative break in trend with the introduction of LLMs (not to say every project is getting better, just that, to the extent they're getting worse, that is the continuation of an existing trend rather than something caused by LLMs). Oh, and more concretely I predict that the number of long-lived vulnerabilities in high-profile projects will be markedly lower as time goes on. It's very reasonable to choose not to interact with LLM-generated code or image generator outputs for moral or aesthetic reasons. None of that has to be grounded in whether LLMs can be used for maintainable, high-quality code. It's convenient when the stance one is morally or aesthetically inclined to take is also the technically superior one, but it doesn't always work out that way.
> — [bakkot on lobsters · 14 points, 2 comments](https://lobste.rs/s/rdhsu9/i_don_t_want_interact_with_stochastic#c_bdtnev)

> > It's convenient when the stance one is morally or aesthetically inclined to take is also the technically superior one, but it doesn't always work out that way. I take that to mean that you don't see the moral and aesthetic arguments against LLMs to be technically grounded? I certainly see the appeal of that stance, though I'm not yet entirely convinced. I wonder what your take is on the problem of LLMs training on their own output? Of course, I don't imagine there's anybody of significance that argues all code should be written by agents. So it's not like we're rapidly descending into the demonic shrill of an AI echo chamber. We can all agree that humans will always need to be somewhere in the loop, the question is: where?  My university training is actually in Religious Studies, which seems a million miles from Computer Science. But we had a module called Religion and Media in which we studied the great communication paradigm shifts of; orality, literacy, printing and digitisation. One book that stood out is _Orality and Literacy: The Technologizing of the Word_, in which it is argued that even poetry and song are technologies. Melody, rhythm and narrative allow information to be more easily remembered (disk drives?) and therefore also allow it to be shared with more people across time and space (the internet?). As we all know from the more recent _digital_ paradigm shift of the last few decades, such technologies can have a profound effect on human culture. LLMs are crucially, by technical definition, not part of this story. They are not rhythm, song, narrative, a system of physical marks that represent spoken language, a machine that faithfully duplicates, nor a protocol for sharing information electronically. They are essentially, as the parent article describes, parrots. Now of course we can also argue that there exist clearly useful parrot-like technologies, for example search engines. So I accept that LLMs are more useful than actual parrots. But the point is that, though they may superficially appear to have a voice, they don't. They do not contribute to any meaningful conversation. Which makes me think our relationship to AI is in fact fundamentally a matter of morals and aesthetics. We all know, or at least should know, that the big AI companies are going to greater, even destructive, lengths to find non-LLM tainted training data. If that is a _technical_ reality, then should it not also be a technical reality that we have a moral and aesthetic responsibility to identify and avoid creating and promoting LLM-tainted content? And I don't mean that from the capitalist perspective of the current economic bubble. I mean it purely from the cold facts of how LLMs need non-LLM training data. Somebody, somewhere has to draw lines and take a stand. The morally or aesthetically superior stance _is_ the technically superior stance. Of course right now there's abundant locally consistent examples of LLM utility, but they underfit the thesis of LLMs' ultimately beneficial contribution to humanity. So let me make a concrete prediction. Any project that does not sincerely reflect on its use of LLMs, though it may well still have maintainable, high-quality code, will eventually fall by the wayside for the simple fact that it is no longer participating in any meaningful conversation with the world in which it claims to support.
> — [tombh on lobsters · 2 points, 1 comments](https://lobste.rs/s/rdhsu9/i_don_t_want_interact_with_stochastic#c_zektde)

> > I take that to mean that you don't see the moral and aesthetic arguments against LLMs to be technically grounded? ... No? I just mean that it is possible to have moral or aesthetic objections to interacting with LLM outputs entirely independently of the question of whether they work (in the sense of producing maintainable code) or will continue working. > I wonder what your take is on the problem of LLMs training on their own output? My understanding is that it turned out that so-called model collapse ended up being pretty easy to avert: you just need some other source of feedback during training, which is part of what has lead to the current regime of Reinforcement Learning from Verifiable Rewards (RLVR). That is to say, my take is that this problem appears to have been basically solved. Labs are seeking out old books because they care about ingesting the factual content of those books, not because they are worried they're going to stop being able to improve the models in the absence of ever more sources of human-produced data to feed into the pretrain. This is an empirical claim about the world. Now, maybe I'm wrong about it. But I don't think it really changes much here, which is my point: it is possible to have moral or aesthetic objections to the technology which hold regardless of the empirical question of whether LLMs training on their own output is ~ a solved problem. > If that is a _technical_ reality, then should it not also be a technical reality that we have a moral and aesthetic responsibility to identify and avoid creating and promoting LLM-tainted content? You are using "technical reality" in some way I'm not really understanding, because this sounds like is-ought conflation to me. > So let me make a concrete prediction. Any project that does not sincerely reflect on its use of LLMs, though it may well still have maintainable, high-quality code, will eventually fall by the wayside for the simple fact that it is no longer participating in any meaningful conversation with the world in which it claims to support. I do love a concrete prediction! Let's nail it down a bit more: would you consider Linux to have sincerely reflected on its use of LLMs? If so, I agree with this prediction but only because I think it's largely vacuous; most big projects sincerely reflect (to some extent) on pretty much any significant change in how the project develops. If not, does that mean you are predicting that Linux will eventually fall by the wayside, and not in the way that all endeavors eventually fall by the wayside? For example, do you think that in, say, 40 years - two generations - we will be able to look around and identify that Linux and other projects which today are accepting use of LLMs will have perished in advance of similar projects that never adopted LLMs?
> — [bakkot on lobsters · 1 points](https://lobste.rs/s/rdhsu9/i_don_t_want_interact_with_stochastic#c_jzxfu0)

**Source threads**

- [lobsters](https://lobste.rs/s/rdhsu9/i_don_t_want_interact_with_stochastic) · 70 points · 25 comments
- [hackernews](https://news.ycombinator.com/item?id=49631476) · 28 points · 61 comments

## Similar posts on daily.dev

- [Bad Vibes Coding](https://daily.dev/posts/bad-vibes-coding-d9novql6h) · Lobsters · 1 upvotes · 1 comments
- [Don't Make Me Talk to Your Chatbot](https://daily.dev/posts/don-t-make-me-talk-to-your-chatbot-kuce3bkn5) · Hacker News · 3 upvotes · 1 comments
- [I can’t bear to read AI-generated prose](https://daily.dev/posts/i-can-t-bear-to-read-ai-generated-prose-hcqk7o4al) · Surfing Complexity · 0 upvotes · 0 comments

---

Tags: [#open-source](https://daily.dev/tags/open-source), [#genai](https://daily.dev/tags/genai), [#chatgpt](https://daily.dev/tags/chatgpt), [#ai-coding](https://daily.dev/tags/ai-coding), [#ethical-ai](https://daily.dev/tags/ethical-ai)

[View this post on daily.dev](https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"I Don’t Want to Interact With Stochastic Parrots","url":"https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc"},"datePublished":"2026-09-09T19:13:02.539Z","dateModified":"2026-09-13T19:35:25.176Z","description":"A personal manifesto rejecting all interaction with AI-generated content, arguing that chatbot text, images, and code are hollow, unmaintainable, and harmful...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/i-don-t-want-to-interact-with-stochastic-parrots-ddabuztwc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,genai,chatgpt,ai-coding,ethical-ai","timeRequired":"PT11M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"I Don’t Want to Interact With Stochastic Parrots"}]}
```

