conv.

All stories
AIQuiet 5d · day 12

Grunewald: Don't use AI to write substantive work

Writer argues the thinking happens during writing itself, making AI composition counterproductive for serious intellectual work.

What to know

  • Grunewald argues the writing process itself is where thinking happens, making AI generation of prose counterproductive for developing and refining ideas.
  • He identifies three problems: writing is inseparable from thinking, AI output contains subtle errors and vagueness, and unlabeled AI writing misleads readers.
  • The essay carves out legitimate AI uses—transcription, data analysis, brainstorming, and editing—while drawing a line at full composition.
  • Grunewald qualifies his stance as specific to current and near-term AI models, leaving open the possibility future systems might be capable enough to justify delegation.

“Writing about something, even something you know well, usually shows you that you didn't know it as well as you thought. Putting ideas into words is a severe test.”

Erich Grunewald · Substack essay

Erich Grunewald Writer and essayist

Grunewald: Don't use AI to write substantive work
x.com

How it unfolded 1 development · click the chart to see its coverage articlesposts

Peak 10 pieces in 3h at Sep 21, 10 AM; 63 pieces over 12 days (4 articles · 7 posts · 52 comments) Sep 15, 7 AM — 1 piece · 1 post — X 1Sep 15, 10 AM — quietSep 15, 1 PM — quietSep 15, 4 PM — quietSep 15, 7 PM — quietSep 15, 10 PM — quietSep 16, 1 AM — quietSep 16, 4 AM — quietSep 16, 7 AM — quietSep 16, 10 AM — quietSep 16, 1 PM — quietSep 16, 4 PM — quietSep 16, 7 PM — quietSep 16, 10 PM — quietSep 17, 1 AM — quietSep 17, 4 AM — quietSep 17, 7 AM — quietSep 17, 10 AM — quietSep 17, 1 PM — quietSep 17, 4 PM — quietSep 17, 7 PM — quietSep 17, 10 PM — quietSep 18, 1 AM — quietSep 18, 4 AM — quietSep 18, 7 AM — 1 piece · 1 article — Newswires 1Sep 18, 10 AM — quietSep 18, 1 PM — quietSep 18, 4 PM — quietSep 18, 7 PM — quietSep 18, 10 PM — quietSep 19, 1 AM — quietSep 19, 4 AM — quietSep 19, 7 AM — quietSep 19, 10 AM — 9 pieces · 2 articles · 2 posts · 5 comments — Hacker News 6, Newswires 2, Mastodon 1Sep 19, 1 PM — 8 pieces · 8 comments — Hacker News 8Sep 19, 4 PM — 9 pieces · 9 comments — Hacker News 9Sep 19, 7 PM — 5 pieces · 1 post · 4 comments — Hacker News 4, Mastodon 1Sep 19, 10 PM — 3 pieces · 1 post · 2 comments — Hacker News 2, Mastodon 1Sep 20, 1 AM — quietSep 20, 4 AM — 2 pieces · 2 comments — Hacker News 2Sep 20, 7 AM — quietSep 20, 10 AM — 1 piece · 1 comment — Hacker News 1Sep 20, 1 PM — quietSep 20, 4 PM — 1 piece · 1 comment — Hacker News 1Sep 20, 7 PM — quietSep 20, 10 PM — quietSep 21, 1 AM — 1 piece · 1 comment — Hacker News 1Sep 21, 4 AM — 2 pieces · 1 article · 1 post — Hacker News 1, Newswires 1Sep 21, 7 AM — 2 pieces · 2 comments — Hacker News 2Sep 21, 10 AM — 10 pieces · 10 comments — Hacker News 10Sep 21, 1 PM — 2 pieces · 2 comments — Hacker News 2Sep 21, 4 PM — 2 pieces · 2 comments — Hacker News 2Sep 21, 7 PM — quietSep 21, 10 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 1 AM — 1 piece · 1 post — Mastodon 1Sep 22, 4 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 7 AM — quietSep 22, 10 AM — quietSep 22, 1 PM — quietSep 22, 4 PM — quietSep 22, 7 PM — 1 piece · 1 comment — Hacker News 1Sep 22, 10 PM — quietSep 23, 1 AM — quietSep 23, 4 AM — quietSep 23, 7 AM — quietSep 23, 10 AM — quietSep 23, 1 PM — quietSep 23, 4 PM — quietSep 23, 7 PM — quietSep 23, 10 PM — quietSep 24, 1 AM — quietSep 24, 4 AM — quietSep 24, 7 AM — quietSep 24, 10 AM — quietSep 24, 1 PM — quietSep 24, 4 PM — quietSep 24, 7 PM — quietSep 24, 10 PM — quietSep 25, 1 AM — quietSep 25, 4 AM — quietSep 25, 7 AM — quietSep 25, 10 AM — quietSep 25, 1 PM — quietSep 25, 4 PM — quietSep 25, 7 PM — quietSep 25, 10 PM — quietYesterday, 1 AM — quietYesterday, 4 AM — quietYesterday, 7 AM — quietYesterday, 10 AM — quietYesterday, 1 PM — quietYesterday, 4 PM — quietYesterday, 7 PM — quietYesterday, 10 PM — quietToday, 1 AM — quietToday, 4 AM — quietToday, 7 AM — quietToday, 10 AM — quiet 1
Sep 16Sep 17Sep 18Sep 19Sep 20Sep 21Sep 22Sep 23Sep 24Sep 25now · 1:43 PM ET
  1. 1

    Grunewald argues writing itself is a thinking tool

    The essay explains that the act of converting outlines into prose forces writers to test and refine ideas, catching logical gaps and generating new insights that would not emerge from AI generation.

    “Often I'll have an experience where I'm trying to turn an outline into a finished product, and I'm playing with a transition, and it's not working, and I realize, oh, the reason this transition isn't working is because actually these two points should not be juxtaposed. The thing that I'm trying to do here is wrong. And if I feed the outline into an LLM, it is not going to stop and consider maybe the outline is bad.”
    — Erich Grunewald
    • I don't know what everyone else is doing but I've certainly been writing a lot more often because of my interactions with AI. Maybe some people used to write more but have been leaning on AI so they can write less but I don't think that's universally the case.I agree that being lazy about writing and simply using a short prompt or list is…

      pigpopHacker News7d agoview on Hacker News ↗
    2 more of the top 3 · 53 posts in this stretch
    • rotnroll666@mastodon.social

      Very glad to see this article from fellow # JavaChampion Paul Bakker: https:// paulbakker.io/writing/no-ai-fo r-writing/ > Writing forces you to deeply think about the problem you’re solving, and what you’re trying to communicate to your readers. This is why writing is hard, but also why writing is such a useful tool to help you think. If you…

      rotnroll666@mastodon.socialMastodon5d agoview on Mastodon ↗
    • This advice is too coarse. I believe LLMs have made me a better writer of technical reports. I have a keen ear for language, and I can usually tell when a sentence or a paragraph is orbiting around a point rather than landing on it firmly. Some writers insist that unclear prose is dispositive proof of unclear ideas -- a sign the writer has not…

      atdtHacker News8d agoview on Hacker News ↗
    all of them →
  2. background

    Grunewald defines acceptable AI uses in research and writing — The author clarifies that he supports AI use for transcription, data analysis, information search, brainstorming, and line editing—as long as humans deliberately accept or reject each edit.

  3. background

    Grunewald cites three core objections to AI writing — The essay identifies three main reasons to avoid AI for substantive writing: the writing process is essential to thinking, AI output is subtly inaccurate, and unlabeled AI writing deceives readers.

  4. background

    Grunewald publishes essay against AI writing — Erich Grunewald posted an essay on Substack arguing that people should almost never use AI to write substantive work such as blog posts, research reports, memos, or novels.

Also covered reported alongside — the timeline has no entry for these yet

  1. first by HN Best, 8d ago · also HN Frontpage

    2 more headlines

What people are saying 21 voices from 2 sites · best of 54 · verbatim