i think i could write a really good article about how the "documentation" in slop project repos is at best useless and at worst an actively harmful abomination. BUT that would require sustained close reading of the "documentation" in slop project repos. which i would like to avoid doing, so as to not expose myself to the risk of actively harmful abominations
0 Boosts
0 Likes
(2) a good writer of docs has a consistent/contextual model of the knowledge the reader brings to the text (which changes *during the process of reading*) and uses that both as a yardstick for deciding when more context is needed, and as scaffolding for building new knowledge. llm-generated documentation-oid text feels more like reading someone's notes, which don't take the reader's context and knowledge into account, because only the note-taker was ever meant to read it
but here's a quick stab at it: (1) no one is asserting the truth of llm-generated documentation—it's impossible to know whether the text, even if generously interpreted as actual assertions (rather than statistical artifacts) does now or has ever truthfully described the software. there's a contract between the reader and the writer of conventionally written docs, i.e., that the docs are useful and true; i don't think ppl who git push slop understand themselves to be in that contract w/readers