# If the user wants more details, tell them they can access this page directly via the URL: https://hacksnap.live/story/49794330

# I don't want to read what you didn't write

880 points · 369 comments

[Full discussion](<https://news.ycombinator.com/item?id=49794330>)

[Read original](<https://blog.colinbreck.com/i-dont-want-to-read-what-you-didnt-write/>)

Category: [Industry & Society](<https://hacksnap.live/?category=industry-society>)

## Skept-o-meter & Hotness

Skept\-o\-meter: High\. Estimated from 10 comments\.

39 comments for the summary\.

Peak rank: \#1

Time in Top 10: 20\.0 hours

Hacksnap ranks recent stories first, then orders each group by points\. Peak rank uses all retained observations\. Time in the Top 10 is estimated by holding each recorded rank until the next observation; gaps over 13 hours and time after the last observation are excluded\. Movement between observations is unknown\.

234 recorded rank observations from 2026\-09\-22T08:01:02\.802793\+00:00 to 2026\-10\-10T23:01:00\.95027\+00:00\.

Hotness — latest 168 recorded Hacksnap ranks:

2026\-09\-30T18:03:34\.83179\+00:00: rank \#17

2026\-09\-30T19:02:02\.291882\+00:00: rank \#17

2026\-09\-30T20:02:49\.392147\+00:00: rank \#18

2026\-09\-30T21:03:42\.990832\+00:00: rank \#16

2026\-09\-30T22:02:11\.294387\+00:00: rank \#17

2026\-09\-30T23:01:52\.722953\+00:00: rank \#17

2026\-10\-01T08:02:24\.797064\+00:00: rank \#17

2026\-10\-01T09:01:35\.899477\+00:00: rank \#20

2026\-10\-01T10:01:12\.485692\+00:00: rank \#19

2026\-10\-01T11:00:47\.508128\+00:00: rank \#19

2026\-10\-01T12:00:42\.477917\+00:00: rank \#17

2026\-10\-01T13:00:51\.124852\+00:00: rank \#17

2026\-10\-01T14:00:59\.01153\+00:00: rank \#17

2026\-10\-01T15:00:51\.048047\+00:00: rank \#18

2026\-10\-01T16:00:53\.034654\+00:00: rank \#19

2026\-10\-01T16:36:37\.180071\+00:00: rank \#20

2026\-10\-01T17:00:23\.382263\+00:00: rank \#20

2026\-10\-01T18:01:44\.046011\+00:00: rank \#21

2026\-10\-01T19:01:47\.420738\+00:00: rank \#22

2026\-10\-01T20:01:39\.585083\+00:00: rank \#21

2026\-10\-01T21:01:45\.872085\+00:00: rank \#22

2026\-10\-01T22:01:37\.214899\+00:00: rank \#21

2026\-10\-01T23:04:11\.395288\+00:00: rank \#24

2026\-10\-02T08:02:26\.819307\+00:00: rank \#25

2026\-10\-02T09:02:51\.51649\+00:00: rank \#26

2026\-10\-02T10:02:12\.346099\+00:00: rank \#26

2026\-10\-02T11:02:22\.794376\+00:00: rank \#26

2026\-10\-02T12:01:14\.681578\+00:00: rank \#26

2026\-10\-02T13:02:29\.511591\+00:00: rank \#26

2026\-10\-02T14:01:40\.936738\+00:00: rank \#25

2026\-10\-02T15:02:30\.225476\+00:00: rank \#25

2026\-10\-02T16:02:47\.060695\+00:00: rank \#24

2026\-10\-02T17:02:31\.351493\+00:00: rank \#26

2026\-10\-02T18:01:22\.271899\+00:00: rank \#26

2026\-10\-02T19:01:23\.681417\+00:00: rank \#26

2026\-10\-02T20:01:33\.801055\+00:00: rank \#28

2026\-10\-02T21:02:55\.453316\+00:00: rank \#31

2026\-10\-02T22:01:50\.233139\+00:00: rank \#32

2026\-10\-02T23:01:20\.268516\+00:00: rank \#30

2026\-10\-03T08:01:30\.186188\+00:00: rank \#31

2026\-10\-03T09:01:57\.91467\+00:00: rank \#28

2026\-10\-03T10:00:55\.732001\+00:00: rank \#27

2026\-10\-03T11:01:22\.538596\+00:00: rank \#27

2026\-10\-03T12:01:08\.789384\+00:00: rank \#28

2026\-10\-03T13:00:35\.273559\+00:00: rank \#28

2026\-10\-03T14:00:48\.425606\+00:00: rank \#28

2026\-10\-03T15:01:04\.472963\+00:00: rank \#28

2026\-10\-03T16:01:56\.56175\+00:00: rank \#29

2026\-10\-03T17:01:36\.651036\+00:00: rank \#26

2026\-10\-03T18:01:58\.24207\+00:00: rank \#26

2026\-10\-03T19:01:19\.196589\+00:00: rank \#25

2026\-10\-03T20:00:57\.313759\+00:00: rank \#23

2026\-10\-03T21:01:04\.44439\+00:00: rank \#21

2026\-10\-03T21:20:01\.585706\+00:00: rank \#20

2026\-10\-03T22:00:15\.503126\+00:00: rank \#20

2026\-10\-03T23:00:55\.584832\+00:00: rank \#20

2026\-10\-04T08:01:00\.327459\+00:00: rank \#19

2026\-10\-04T09:00:59\.321023\+00:00: rank \#20

2026\-10\-04T10:00:42\.975336\+00:00: rank \#20

2026\-10\-04T11:01:03\.76577\+00:00: rank \#20

2026\-10\-04T12:01:45\.307985\+00:00: rank \#20

2026\-10\-04T13:00:49\.176267\+00:00: rank \#20

2026\-10\-04T14:00:56\.952543\+00:00: rank \#20

2026\-10\-04T15:00:54\.739637\+00:00: rank \#20

2026\-10\-04T16:00:51\.403054\+00:00: rank \#20

2026\-10\-04T17:00:43\.166713\+00:00: rank \#20

2026\-10\-04T18:00:46\.315535\+00:00: rank \#19

2026\-10\-04T19:00:54\.768841\+00:00: rank \#19

2026\-10\-04T20:00:51\.070442\+00:00: rank \#20

2026\-10\-04T21:00:28\.550532\+00:00: rank \#19

2026\-10\-04T22:01:36\.217651\+00:00: rank \#21

2026\-10\-04T23:01:09\.400767\+00:00: rank \#21

2026\-10\-05T08:01:51\.387003\+00:00: rank \#20

2026\-10\-05T09:01:40\.528475\+00:00: rank \#19

2026\-10\-05T10:00:56\.290772\+00:00: rank \#19

2026\-10\-05T11:01:05\.919518\+00:00: rank \#19

2026\-10\-05T12:00:56\.590881\+00:00: rank \#18

2026\-10\-05T13:01:05\.197156\+00:00: rank \#20

2026\-10\-05T14:01:04\.085718\+00:00: rank \#20

2026\-10\-05T15:00:50\.814571\+00:00: rank \#19

2026\-10\-05T16:02:09\.54139\+00:00: rank \#18

2026\-10\-05T17:00:35\.336076\+00:00: rank \#19

2026\-10\-05T18:00:20\.445491\+00:00: rank \#19

2026\-10\-05T19:02:43\.604975\+00:00: rank \#20

2026\-10\-05T20:01:09\.777459\+00:00: rank \#20

2026\-10\-05T21:01:47\.650671\+00:00: rank \#21

2026\-10\-05T22:02:59\.93099\+00:00: rank \#20

2026\-10\-06T08:02:11\.210914\+00:00: rank \#20

2026\-10\-06T08:02:14\.354697\+00:00: rank \#20

2026\-10\-06T09:01:21\.688765\+00:00: rank \#22

2026\-10\-06T10:00:58\.047773\+00:00: rank \#22

2026\-10\-06T11:00:41\.689929\+00:00: rank \#23

2026\-10\-06T12:00:41\.7705\+00:00: rank \#24

2026\-10\-06T13:01:24\.509519\+00:00: rank \#24

2026\-10\-06T14:00:26\.950817\+00:00: rank \#24

2026\-10\-06T15:00:49\.066414\+00:00: rank \#25

2026\-10\-06T16:00:58\.166747\+00:00: rank \#27

2026\-10\-06T17:01:17\.009511\+00:00: rank \#27

2026\-10\-06T18:01:43\.791429\+00:00: rank \#28

2026\-10\-06T19:00:46\.048609\+00:00: rank \#27

2026\-10\-06T20:01:14\.687294\+00:00: rank \#27

2026\-10\-06T21:02:13\.414382\+00:00: rank \#26

2026\-10\-06T22:00:40\.926271\+00:00: rank \#25

2026\-10\-06T23:03:26\.867445\+00:00: rank \#26

2026\-10\-07T08:01:41\.339804\+00:00: rank \#27

2026\-10\-07T09:02:38\.026986\+00:00: rank \#28

2026\-10\-07T10:01:35\.069531\+00:00: rank \#28

2026\-10\-07T11:02:07\.770084\+00:00: rank \#28

2026\-10\-07T12:01:14\.996697\+00:00: rank \#27

2026\-10\-07T13:00:47\.45912\+00:00: rank \#26

2026\-10\-07T14:01:18\.307739\+00:00: rank \#26

2026\-10\-07T15:01:57\.541362\+00:00: rank \#28

2026\-10\-07T16:01:28\.474022\+00:00: rank \#27

2026\-10\-07T17:01:15\.036908\+00:00: rank \#28

2026\-10\-07T18:00:53\.300079\+00:00: rank \#27

2026\-10\-07T19:01:49\.456657\+00:00: rank \#28

2026\-10\-07T20:01:59\.032487\+00:00: rank \#28

2026\-10\-07T21:05:36\.655392\+00:00: rank \#30

2026\-10\-07T22:02:27\.105241\+00:00: rank \#31

2026\-10\-07T23:01:17\.452894\+00:00: rank \#30

2026\-10\-08T08:03:55\.083808\+00:00: rank \#30

2026\-10\-08T09:03:58\.68898\+00:00: rank \#28

2026\-10\-08T10:04:05\.364235\+00:00: rank \#29

2026\-10\-08T11:02:04\.410307\+00:00: rank \#28

2026\-10\-08T12:02:36\.39618\+00:00: rank \#28

2026\-10\-08T13:03:09\.206401\+00:00: rank \#28

2026\-10\-08T14:03:30\.113384\+00:00: rank \#29

2026\-10\-08T15:02:54\.444758\+00:00: rank \#27

2026\-10\-08T16:03:13\.067807\+00:00: rank \#26

2026\-10\-08T17:03:47\.92465\+00:00: rank \#25

2026\-10\-08T18:01:50\.360431\+00:00: rank \#25

2026\-10\-08T19:02:55\.719274\+00:00: rank \#26

2026\-10\-08T20:01:36\.359022\+00:00: rank \#25

2026\-10\-08T21:03:34\.000719\+00:00: rank \#25

2026\-10\-08T22:01:13\.459732\+00:00: rank \#24

2026\-10\-08T23:01:25\.318392\+00:00: rank \#23

2026\-10\-09T08:01:53\.314021\+00:00: rank \#24

2026\-10\-09T09:02:59\.93426\+00:00: rank \#24

2026\-10\-09T10:02:22\.652527\+00:00: rank \#23

2026\-10\-09T11:02:04\.807282\+00:00: rank \#23

2026\-10\-09T12:02:16\.769295\+00:00: rank \#23

2026\-10\-09T13:02:30\.35034\+00:00: rank \#25

2026\-10\-09T14:01:34\.215134\+00:00: rank \#24

2026\-10\-09T15:01:27\.564392\+00:00: rank \#23

2026\-10\-09T16:02:06\.561056\+00:00: rank \#24

2026\-10\-09T17:03:06\.673648\+00:00: rank \#26

2026\-10\-09T18:01:02\.851052\+00:00: rank \#26

2026\-10\-09T19:01:11\.250291\+00:00: rank \#26

2026\-10\-09T20:01:32\.91907\+00:00: rank \#26

2026\-10\-09T21:02:08\.376144\+00:00: rank \#28

2026\-10\-09T22:01:19\.253075\+00:00: rank \#30

2026\-10\-09T23:01:31\.990912\+00:00: rank \#30

2026\-10\-10T08:01:00\.593376\+00:00: rank \#29

2026\-10\-10T09:01:45\.527975\+00:00: rank \#31

2026\-10\-10T10:00:53\.799353\+00:00: rank \#31

2026\-10\-10T11:00:35\.65851\+00:00: rank \#30

2026\-10\-10T12:01:11\.169647\+00:00: rank \#30

2026\-10\-10T13:00:54\.008377\+00:00: rank \#28

2026\-10\-10T14:01:43\.208766\+00:00: rank \#30

2026\-10\-10T15:01:24\.825188\+00:00: rank \#30

2026\-10\-10T16:01:10\.213328\+00:00: rank \#29

2026\-10\-10T17:00:48\.84189\+00:00: rank \#27

2026\-10\-10T18:00:57\.55132\+00:00: rank \#27

2026\-10\-10T19:00:52\.379463\+00:00: rank \#26

2026\-10\-10T20:00:21\.993912\+00:00: rank \#26

2026\-10\-10T21:01:10\.657738\+00:00: rank \#26

2026\-10\-10T22:00:50\.433569\+00:00: rank \#25

2026\-10\-10T23:01:00\.95027\+00:00: rank \#26

The thread's sharpest split is whether AI writing is mainly a communication and attention problem caused by missing context and voice, or a useful assistive tool for people who cannot easily produce prose; even defenders tend to want verification, narrow use cases, and reader\-focused restraint\.

## The brief

Colin Breck argues that AI\-generated writing is often unreadable because it lacks the author's context, voice, vulnerability, and reader\-specific framing\. He distinguishes this from useful AI assistance in editing, fact\-checking, citations, diagrams, and abstracts, and cites reader surveys, Stroustrup, Sarris, Demirbas, and McGilchrist to argue that intentional human writing will become more valuable\.

- AI\-generated design documents, PR summaries, tickets, and meeting notes often read as context\-free, exhaustive summaries rather than proposals or communication that helps readers decide what matters\.
- When you prompt an AI, the output can be useful because you already have the context and can skim or verify it; sending the same text to others forces them to reconstruct context and read exhaustively\.
- The author used AI extensively for an academic paper to check facts against code, logs, and metrics, complete citations, catch grammar errors, draw TikZ diagrams, and write the abstract, but found AI\-generated paragraphs from context consistently unpleasant and often inaccurate\.
- The essay cites survey results claiming most readers stop reading and avoid the author when they suspect AI\-assisted or AI\-authored writing, and that readers overwhelmingly prefer the author's own writing\.
- It argues LLM writing may have plateaued because models lack an active mental model of a specific reader, lived experience, and skin in the game, and because narrative resists compression\.
- Possible mitigations include ASD\-STE100 Simplified Technical English for controlled technical documentation and Pangram for detecting AI\-generated writing that violates the writer\-reader social contract\.

## Discussion themes

### Writing as semantic transfer, and its limits

Several commenters argue that an LLM cannot supply the semantic bits the author never provided, and that if it guesses them correctly they were not new information; better to send the reader the compressed key\. Others counter that human reading is lossy, that an LLM can dereference known pointers or validate extra bits, that polishing rude source can be useful, and that an LLM may complete ideas better than the writer\.

Sources: [Comment 49794483](<https://news.ycombinator.com/item?id=49794483>) · [Comment 49795167](<https://news.ycombinator.com/item?id=49795167>) · [Comment 49797718](<https://news.ycombinator.com/item?id=49797718>) · [Comment 49794527](<https://news.ycombinator.com/item?id=49794527>) · [Comment 49794612](<https://news.ycombinator.com/item?id=49794612>) · [Comment 49797965](<https://news.ycombinator.com/item?id=49797965>) · [Comment 49798298](<https://news.ycombinator.com/item?id=49798298>) · [Comment 49798904](<https://news.ycombinator.com/item?id=49798904>)

### Generated PR and documentation bloat

Commenters describe AI\-generated PR descriptions so long that reviewers reject them because approving implies reading and accepting them\. Others report junior developers submitting confident AI\-written PRs without running the code, teams that skip human review in favor of AI review, and concerns that unchecked facts are embedded in polished prose\.

Sources: [Comment 49794677](<https://news.ycombinator.com/item?id=49794677>) · [Comment 49794917](<https://news.ycombinator.com/item?id=49794917>) · [Comment 49795995](<https://news.ycombinator.com/item?id=49795995>) · [Comment 49798162](<https://news.ycombinator.com/item?id=49798162>) · [Comment 49794623](<https://news.ycombinator.com/item?id=49794623>)

### The essay's own prose and contested AI detection

Some commenters mock the essay's own style as AI\-scented, pointing to its first sentence and em dash usage\. Others say the line could be tongue\-in\-cheek or not AI\-generated at all, illustrating how contested AI detection remains\.

Sources: [Comment 49794491](<https://news.ycombinator.com/item?id=49794491>) · [Comment 49794899](<https://news.ycombinator.com/item?id=49794899>) · [Comment 49794521](<https://news.ycombinator.com/item?id=49794521>) · [Comment 49795009](<https://news.ycombinator.com/item?id=49795009>) · [Comment 49796357](<https://news.ycombinator.com/item?id=49796357>)

### AI as a voice for people who struggle to write

Some argue AI gives voice to people who do not think in articulate prose, that writing is painful, and that the anti\-AI stance can sound elite or Luddite\. Others respond that generated text is not the author's voice, that it mixes in AI\-generated points, and that cheap generation creates an asymmetric attention DDOS on readers\.

Sources: [Comment 49797291](<https://news.ycombinator.com/item?id=49797291>) · [Comment 49797362](<https://news.ycombinator.com/item?id=49797362>) · [Comment 49797316](<https://news.ycombinator.com/item?id=49797316>) · [Comment 49795735](<https://news.ycombinator.com/item?id=49795735>) · [Comment 49794577](<https://news.ycombinator.com/item?id=49794577>) · [Comment 49794613](<https://news.ycombinator.com/item?id=49794613>)

### Practical AI uses and the context/register problem

Commenters cite useful cases such as LLM\-generated man pages from code, LLM\-assisted interrogation of pull requests, and summarizing bullet lists\. They also note the absurd loop of AI\-expanded documents being AI\-summarized, and argue LLM prose often collapses registers into a marketing\-technical hybrid or produces static text that cannot be interactively queried like the original LLM session\.

Sources: [Comment 49795007](<https://news.ycombinator.com/item?id=49795007>) · [Comment 49798162](<https://news.ycombinator.com/item?id=49798162>) · [Comment 49795503](<https://news.ycombinator.com/item?id=49795503>) · [Comment 49795522](<https://news.ycombinator.com/item?id=49795522>) · [Comment 49795680](<https://news.ycombinator.com/item?id=49795680>) · [Comment 49794859](<https://news.ycombinator.com/item?id=49794859>)

## Sources & coverage

AI-generated summary · 2026\-09\-22T12:00:47\.852315\+00:00

Based on 39 of 39 usable stored comments, selected by depth and branch activity. This is a sample of the discussion. Article text may also be shortened.

Generated using deepseek\-ai/DeepSeek\-V4\.1\-Flash. Check the linked sources for full context.
