Gotta say this site is killing it in the LLM-written technical blog SEO game the last couple years, they're consistently able to dominate (and actual deliver in spite of the LLM-isms) SERP for a set of technologies that very closely align with the ones that a typical backend/infrastructure engineer would work on.
I checked their list of blog articles from the last year and they haven't even written that many, which makes it quite impressive because they really model the set that I've been working with (Go, Postgres, grpc, otel) well by I guess defining some kind of customer archetype and writing really detailed guides about what they'd be interested in learning more about. At this point I've encountered their site "organically" like 5x in the last year and recognize the name/style of content so they're doing something right in the marketing department for sure.
On one hand you could just dismiss it as spam but articles like this actually represent a pretty significant LLM spend/human review element that delivers real value to me as a technical end user looking for info on google or in technical blogs on HN (ie it would take me a long time to generate something like this myself and I wouldn't do it proactively, only when-needed). So it actually does help me quite a bit that they do so before I think to ask about it.
I came to the comments to see the discussion and almost all of them are just complaining about LLM-assisted writing.
It's exhausting and tedious, like people nitpicking grammar.
It's also off-topic. I'd love it if HN banned (or strongly discouraged) this kind of repetitive low-value off-topic meta-discussion.
We get it, LLMs are used to write now. Some people don't like it. No need to broadcast that dislike every time, it adds noise to the discussion. :-(
(yes I realize I am also adding off-topic noise but this thread was nothing but that, so I guess I am on-topic until actual Postgres discussion starts).
`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 (not that something can go wrong, I just feel anxiety hehe)
The features look exciting, but the article is exceptionally unclear to me. I am not sure whether that is my fault, the author's, or the LLM's who wrote it.
I checked their list of blog articles from the last year and they haven't even written that many, which makes it quite impressive because they really model the set that I've been working with (Go, Postgres, grpc, otel) well by I guess defining some kind of customer archetype and writing really detailed guides about what they'd be interested in learning more about. At this point I've encountered their site "organically" like 5x in the last year and recognize the name/style of content so they're doing something right in the marketing department for sure.
On one hand you could just dismiss it as spam but articles like this actually represent a pretty significant LLM spend/human review element that delivers real value to me as a technical end user looking for info on google or in technical blogs on HN (ie it would take me a long time to generate something like this myself and I wouldn't do it proactively, only when-needed). So it actually does help me quite a bit that they do so before I think to ask about it.
It's exhausting and tedious, like people nitpicking grammar.
It's also off-topic. I'd love it if HN banned (or strongly discouraged) this kind of repetitive low-value off-topic meta-discussion.
We get it, LLMs are used to write now. Some people don't like it. No need to broadcast that dislike every time, it adds noise to the discussion. :-(
(yes I realize I am also adding off-topic noise but this thread was nothing but that, so I guess I am on-topic until actual Postgres discussion starts).
The headline feature (property graphs) has a better example here in the official docs: https://www.postgresql.org/docs/19/ddl-property-graphs.html
It's off-putting to me too. I wonder if the AI enthusiasts that stopped manually writing also find it off-putting
It’s only when you generate a blog post that I get the ick from slop.
Because I clearly put effort into my blog post and you did not.