README, not

Lobsters Hottest News

Summary

A blog post proposes adding a READMENOT file to projects to clearly indicate that the code is AI-generated slop not intended for direct human reading, helping users avoid wasting attention on machine outputs.

<p><a href="https://lobste.rs/s/wveduf/readme_not">Comments</a></p>
Original Article
View Cached Full Text

Cached at: 07/16/26, 01:56 PM

# README, not Source: [https://blog.yossarian.net/2026/07/16/README-not](https://blog.yossarian.net/2026/07/16/README-not) ## ENOSUCHBLOG ## *Programming, philosophy, pedaling\.* - [Home](https://blog.yossarian.net/) - [Tags](https://blog.yossarian.net/tags) - [Series](https://blog.yossarian.net/series) - [Favorites](https://blog.yossarian.net/favorites) - [Archive](https://blog.yossarian.net/archive) - [Main Site](https://yossarian.net/) - [TILs](https://yossarian.net/til) --- ## *Jul 16, 2026*Tags:[ai](https://blog.yossarian.net/tags#ai),[oss](https://blog.yossarian.net/tags#oss) --- ![Borat saying "not"](https://blog.yossarian.net/assets/borat-not.png) \(Thanks to[Facundo Tuesca](https://github.com/facutuesca)for the name inspiration\)\. If you’re like me, you spend a lot of your working day \(and a good chunk of your personal time\) reading code online\. Increasingly, that means accidentally reading a lot of “slop”[1](https://blog.yossarian.net/2026/07/16/README-not#fn:slop)\. Personally, slop isn’t annoying*per se*[2](https://blog.yossarian.net/2026/07/16/README-not#fn:codegen): it’s okay for personal software[3](https://blog.yossarian.net/2026/07/16/README-not#fn:personal), for example, to be slop\. What makes slop annoying is the feeling of being bait\-and\-switched: much like the written word, I want to be*informed*[4](https://blog.yossarian.net/2026/07/16/README-not#fn:informed)before I spend my human attention on machine outputs\. I’m a big believer in giving people a way to express honest intentions\. For example, I*do*sometimes want to drop some slop on the Internet \(to save for myself later, or for others to reuse without reading\), but I don’t want to mislead people about the intent or effort behind it\. So: what if we gave people a way to express their honest intentions with slop? We use`README`files to tell users where to start when reading a project; I think we should have a`READMENOT`[5](https://blog.yossarian.net/2026/07/16/README-not#fn:naming)file that users \(or their agents\) can add to their projects when they’re slopping it up\. The presence of that file would serve as an unambigous warning that the code within the project is unsuitable for*unwitting*human comprehension[6](https://blog.yossarian.net/2026/07/16/README-not#fn:comprehension)\. A`READMENOT`could contain anything, but it seems to me like a good default would be a short human\-friendly explanation of*why*the project shouldn’t be read\. For example: ``` 1 2 3 4 5 Warning! You're reading a project that isn't intended for direct human consumption. You may wish to use an LLM or another tool to interact automatically with this project. ``` --- ---

Similar Articles

Reviewing code requires reading

Lobsters Hottest

A developer blog post argues against the idea of shipping AI-generated code to production without reading it, emphasizing that code review serves critical purposes: diffusing responsibility, reducing bus factor, and maintaining team knowledge of the codebase.

Quoting Kenton Varda

Simon Willison's Blog

Kenton Varda announces a moratorium on AI-written change descriptions (PR/commit messages, issues/tickets) on his team, citing that AI omits high-level framing needed for code review and produces worse-than-useless descriptions.