Theme 1 – Criticism of LLM/AI‑written style
Many commenters find the prose “sloppy,” nauseating, or lacking substance because it feels generated by a language model.
- “Tangential, but the Claude‑isms make it a less rewarding read” – zdc1
- “It is getting quite nauseating to see Claude's fingerprints all over the page and at this point I just expect the slop to continue.” – rvz
- “I just can’t get over that slightly detached, nauseating feeling that follows the realization that I just read 3 long sentences that said very little.” – WD-42
- “The problem is not just the writing style, but rather that it doesn't make sense at all … This level of disdain for readers is beyond belief.” – exceptione
Theme 2 – Praise for the article’s practical utility / SEO value
Despite the AI‑ish tone, readers appreciate the concrete examples, the site’s topical relevance, and the time‑saved lookup it provides.
- “Gotta say this site is killing it in the LLM‑written technical blog SEO game … they actually represent a pretty significant LLM spend/human review element that delivers real value to me as a technical end user … So it actually does help me quite a bit that they do so before I think to ask about it.” – weitendorf
- “The way I process this kind of content is by skimming or ctl‑Fing for the material I'm interested in … I'd prefer the LLM‑assisted article most of the time.” – weitendorf
- “on conflict do select and eager aggregation are the most notable for me, I use upserts and joins like that all the time. Annual postgres upgrades are always exciting (features) and terrifying (ops) :D” – sysashi
Theme 3 – Calls for greater clarity, detail, and better examples
Several users suggest adding EXPLAIN statements, basic SELECT queries, or more explicit explanations to make the demo truly instructive.
- “I’d pair each example with EXPLAIN (ANALYZE, BUFFERS) so readers can see when the planner’s choice changes on a real workload. A short note about statistics freshness and extended statistics would also help …” – quarrykit
- “You can add the following statements in the first example and click 'Run' button in order to understand the underlying tables' structure and contents … SELECT * FROM person; SELECT * FROM follows;” – valyala
- “The example makes zero sense, because the fucking tables aren't even there.” – exceptione
- “I am interested in what features postgresql 19 has … and would like to see a summary that starts with a bullet list of highlights.” – jgord