Caleb Gross’s “You can just say it” makes a clean argument about human intent in AI: defending people by saying they still outperform models is a weak move. The stronger claim is simpler. Humans matter before the comparison starts, and creative work should be judged by more than surface polish.
Table of Contents
The short version
- Gross argues that tying human worth to better output than AI is fragile because model capability keeps moving.
- His sharper definition of AI slop is work with form but little readable intent, not merely bad work or machine-made work.
- The Hacker News discussion mostly found the intent framing useful, especially for writing, email, and AI-assisted coding.
- The hard question is whether readers can still feel a person’s judgment when AI has cleaned up every sentence.
What happened
Caleb Gross published “You can just say it” on May 28, 2026. The essay pushes back on a common defense of human value in the age of generative AI: people are special because they can still do some things better than machines.
That argument may feel reassuring for a while. It also makes human dignity depend on the next benchmark run. Gross’s alternative is intentionally plain: humans are valuable. You do not need to attach that claim to writing speed, design quality, coding productivity, or any other measure of output.
The essay then moves from human value to creative quality. Gross describes creation as intent taking form. A resignation letter, a drawing, a design, a piece of code, or a message all carry some mix of what the maker meant and what the maker produced. Generative AI changes that balance because it can produce convincing form from a thin prompt.
That is where the essay’s useful definition of AI slop appears. Slop is not automatically “content made with AI.” It is output where the intent is hard to find. A human can make it. A person using AI can avoid it. The difference is whether judgment, taste, and purpose remain visible.
Why this is worth watching: human intent in AI
The phrase human intent in AI can sound abstract until you apply it to ordinary work. Think about the email example in the essay. If someone uses a model to turn a blunt request into a long, polite message, the result may be smoother. It may also make the recipient work harder to infer what the sender actually wants.
That matters for product teams and app builders. AI writing tools often sell polish: clearer tone, better structure, faster drafting. Polish is useful. The risk is that a product can make every message sound finished while removing the cues that tell the reader what the sender chose, cared about, or understood.
The same applies to AI-assisted coding. A generated patch can look complete. The better question is whether the prompts, review comments, tests, and edits add up to a coherent specification. If they do, AI is helping a human express intent. If they do not, the model may be producing code-shaped material that nobody fully owns.
For more coverage of AI product and developer-tool debates, see the IT & AI archive.
What Hacker News readers are arguing about
The main Hacker News thread was unusually substantive for an AI culture argument: 383 points and more than 200 extracted comments. The most productive camp liked the essay because it separated a complaint about AI misuse from a blanket complaint about AI itself.
One widely upvoted line of discussion treated the essay’s slop definition as a better mental model for AI-assisted coding. The useful distinction was between a chain of prompts that forms a real specification and a chain of retries that amounts to “it does not work, try again.” In the first case, the human is still steering. In the second, the human may be outsourcing responsibility.
Another cluster focused on communication. Several commenters reacted to the quoted line about preferring the raw prompt over an AI-written email. The shared irritation was not that a machine touched the prose. It was that the sender might be asking the reader to decode a polished message the sender did not bother to write or fully understand.
There was also pushback. Some readers disliked the essay’s religious reference to Genesis as support for human value, even when they agreed with the broader claim. Others argued over whether “valuable” was the right word at all, since it can imply something measurable. “Invaluable” felt closer to what some commenters wanted to say.
The liveliest disagreement was about intent itself. One commenter prompted Claude to make something unconstrained and asked how anyone could be sure there was no intent in the result. Replies split between people who saw that as anthropomorphism and people who thought dismissing machine intent by saying “it is numbers” was too glib. That argument is not settled by Gross’s essay, but the essay gives readers a cleaner vocabulary for having it.
The practical read
If you are building with generative AI, the practical test is not “did AI touch this?” That question is already too blunt. Ask whether a reader, user, or teammate can still see the human intent in AI-assisted work.
For writing tools, that means preserving the user’s point rather than inflating it into generic professional language. For coding tools, it means making review, tests, and constraints visible enough that the generated output has a responsible owner. For content teams, it means rejecting pieces that look finished but do not seem to come from anyone in particular.
This is also a useful editorial standard. Bad AI output is easy to mock. Polished, empty output is harder to catch because it passes a quick scan. Gross’s essay is worth reading because it names that problem without pretending the answer is to avoid every AI tool.
Human intent in AI is not nostalgia for manual labor. It is the part that tells another person, “someone meant this.” When that disappears, even technically competent output starts to feel cheap.