Fetching from the wire…
01
02
03
04
05
06
07
08
Policy2026-08-02 · source-backed
Isaac Su argues that announcing LLM use when presenting code is like a writer disclosing their spellchecker: since an LLM can't be held responsible for a mistake, crediting it quietly transfers away accountability that should stay with you. He offers four motives: guilt about automation, hoping impressive output reflects better on the tool, avoiding review work, and pre-emptive cover for sloppy work. No actual organizational or academic attribution policies cited, so it's argument rather than evidence. 39 comments on 32 points means people disagree. It also lands the same week as Astra, where the entire framing question is whether a model "solved" the problems or a research process did.
Each link below shares sources, entities, or timing with this story.
Simon Willison released LLM / Shared entity: LLM / Shared topic / Earlier coverage
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; overlapping topics (code, disagree).
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; overlapping topics (automation, code).
Simon Willison released LLM / Shared entity: LLM / Earlier coverage / Tension
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-07-27.
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-06-19.
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-06-18.
Simon Willison released LLM / Shared entity: LLM / Earlier coverage
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-07-31.
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-06-19.
Linked by a graph relationship (Simon Willison released LLM); both cover LLM; earlier LLM coverage from 2026-07-19.