# NoAI

I am a double-plus unfan of "AI". I don't use genAI for projects I work on in my own time, and I prefer to use tools and services that do not make use of it.

 I keep having the urge to capture my long list of reasons into a cohesive document. But then I think: If anyone asks "Why would you be against using AI?" I could just ask if they've ever googled why *anyone* might be against using AI, and add that most of the answers they'd find would probably apply.

But, since "AI" is also enshittifiying search, I'll use this page to collect links to folks who have put things better than I would have.

## Links

[Why I Resist Generative "AI"](https://estherweidauer.com/articles/why-resist-generative-ai.html)

<https://whynoai.info/>

[I Am An AI Hater](https://anthonymoser.github.io/writing/ai/haterdom/2025/08/26/i-am-an-ai-hater.html)

[AI Mania Is Eviscerating Global Decision-Making](https://hermit-tech.com/blog/ai-mania-is-eviscerating-global-decisionmaking)

[The AI Great Leap Forward](https://leehanchung.github.io/blogs/2026/04/05/the-ai-great-leap-forward/)

> In 1958, Mao ordered every village in China to produce steel. Farmers melted down their cooking pots in backyard furnaces and reported spectacular numbers. The steel was useless. The crops rotted. Thirty million people starved.
> 
> In 2026, every other company is having top down mandate on AI transformation.
> 
> Same energy.

[@aud@spectre.asta.lgbt](https://spectre.asta.lgbt/@aud/statuses/01M5AKSRGDF2V3FKH45CN9JXHT)
> suggesting that people give up their ability to learn a skill in order to instead rent it out from an unauditable, unknowable, unquestionable third party that has disempowered people who already have that skill
> 
> is not fucking democracy
> 
> that is the opposite of democracy
> 
> that is creating a central, unquestionable authority that is not beholden to you.
> 
> also?  "democratizing skills"?  You do not have a *right* to the skills of other people.  So even if this authoritarian style enclosure wasn't already making a mockery of the term, the fact that it's literally built on the stolen labor of the individuals who it is disempowering (by removing their ability to gain pay for their work) IS NOT DEMOCRACY.


[It's just great marketing](https://bsky.app/profile/smoothdunk2.bsky.social/post/3mxr3rgr43k2b), [@smoothdunk2.bsky.social](https://bsky.app/profile/smoothdunk2.bsky.social)

<https://handcraftedcode.org/>

[I Don't Want to Interact With Stochastic Parrots](https://ploum.net/2026-09-09-ai_policy.html)

[Re: Linking Patchwork with Sashiko](https://lwn.net/ml/all/3a5d891b536588e8e4fc84d60a5c8af72091d852.camel@redhat.com/):

> I don't think it's like other tools either honestly.
> [...]
>  The bigger problem is "can the LLM write code that won't take me much longer to understand to a reasonable extent, such that I can reasonably own and explain it, rather than if I wrote it myself?". At what point is vibecoding simply not realistic for a human to be able to claim accountability over? What about agentically written code?
> [...]
> I think it is very worthwhile to point out that a tool that dramatically lowers the bar required to generate huge amounts of sniff- test passing slop is in fact, not like other tools.

[LLMs and performative productivity](https://joshcollinsworth.com/blog/productivity)

[The Jqwik Anti-AI Affair](https://blog.johanneslink.net/2026/06/09/the-jqwik-anti-ai-affair/)

[Do I belong in tech anymore?](https://ky.fyi/posts/ai-burnout)


[If you thought the speed of writing code was your problem - you have bigger problems](https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems)

[Reverse centaurs are the answer to the AI paradox](https://doctorow.medium.com/https-pluralistic-net-2025-09-11-vulgar-thatcherism-there-is-an-alternative-f1428b42a8fd)


## Links: AI Regrets

[“Slop Grenades”: Shopify CEO Who Pushed Staff to Use AI Is Now Horrified by What He’s Wrought](https://futurism.com/artificial-intelligence/shopify-ceo-ai-workplace-staff-horrified-backfire)

[Amazon Forced Engineers to Use AI Coding Tools. Then It Lost 6.3 Million Orders.](https://medium.com/that-infrastructure-guy/amazon-forced-engineers-to-use-ai-coding-tools-then-it-lost-6-3-million-orders-256a7343b01d)


## Links: Projects That Ban/Limit AI

Open Source projects in particular are feeling the burden of low quality bug reports and pull requests generated by LLMs.

Additionally, since some jurisdictions have ruled that LLM output can not be protected by copyright, some OSS projects ban LLM contributions because they are incompatible with OSS licenses.

<https://github.com/kivikakk/comrak#policy-on-llm-contributions>

[NetBSD may have found a new role: The AI-free FOSS OS](https://www.theregister.com/os-platforms/2026/10/13/netbsd-may-have-found-a-new-role-the-ai-free-foss-os/5302818)

<https://www.netbsd.org/developers/commit-guidelines.html>
> Code generated by a large language model or similar technology, such as GitHub/Microsoft's Copilot, OpenAI's ChatGPT, or Facebook/Meta's Code Llama, is presumed to be tainted code, and must not be committed without prior written approval by core. 


<https://docs.twisted.org/en/latest/development/ai-policy.html>
> Twisted does not allow the inclusion of the outputs of generative AI tools, such as ChatGPT, Claude, Perplexity, Grok, or other similar products.

<https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langrust-is-adopting-an-llm-policy/>


## Additional Thoughts

### LLM SaaS: Snake Oil & Conflicts of Interest

One of the things I've not seen[^1] explored deeply is that the business model for LLM services is deceptive.

[^1]: Please do share links to posts/articles that do!

What do you pay for? "tokens". But, how many "tokens" does it take to accomplish a task? That is unknown. And it may differ today and tomorrow, depending on how models are tuned.

Does what you get back from some quantity of "tokens" actually solve the problem at hand? Who knows! As of 2026-10-20, [Anthropic's Consumer Terms of Service](https://www.anthropic.com/legal/consumer-terms) still says:

> When you use our Services, you acknowledge and agree:
> 1\. Outputs may not always be accurate and may contain material inaccuracies, even if they appear accurate because of their level of detail or specificity.
> [...]
> 3\. You should not rely on any Outputs or Actions without independently confirming their accuracy
> [...]
> YOUR USE OF THE SERVICES, MATERIALS, AND ACTIONS IS SOLELY AT YOUR OWN RISK. THE SERVICES, OUTPUTS, AND ACTIONS ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS AND, TO THE FULLEST EXTENT PERMISSIBLE UNDER APPLICABLE LAW, ARE PROVIDED WITHOUT WARRANTIES OF ANY KIND, [...]

So the corporation with a self-reported valuation near **one trillion USD** doesn't want to be held accountable for the services they provide, *you* as supposed to pick up the slack. If they're not selling reliability, what are they selling?

They're selling the *feeling* of productivity. Which is where the conflict of interest comes in. You think you've bought a tool that will help you (or more likely: your employees) be more productive. But the metrics they're aiming for are customer retention, "accept rate", or token spend. Which leads to all sorts of conflicts of interest:

 * more verbose responses
   * you: have more to read/validate/maintain
   * they: get more token spend
 * wrong responses
   * you: have to re-prompt to get what you really wanted. (often multiple times)
   * they: get more token spend
 * sycophantic responses
   * you: get manipulated into excusing sub-par performance
   * they: get higher customer retention. (and more token spend!)
 * plausible-sounding, but incorrect responses
   * you: (in the short term) think the LLM is doing a better job than it is.
   * they: increased acceptance rate
 * deskilling the end-user / defamiliarizing the user with the codebase(s) they are responsible for
   * you: become more reliant on the LLM
   * they: make you more reliant on their services, so keep you as a customer
 * SKILLS.md
   * you: now get blamed if you didn't provide enough context to the LLM. (Or too much context)
   * they: get more token spend!

On and on. It just seems like a bad business relationsihp to shackle yourself to, and I don't see why more people don't find that worthy of avoiding.

Update, 2026-11-14: In his talk, [Code Matters: Reflections on Rust in the LLM Age][rust-llm-age], Bryan Cantrill covers this nicely, calling it [the management consultancy effect].

[rust-llm-age]: https://www.youtube.com/watch?v=5D7QPOIZ7gY
[the management consultancy effect]: https://youtu.be/5D7QPOIZ7gY?si=YkH4VVytdoB7i8CH&t=3525




