4 ms·

I understand your point. But my contention is that there is a lot of spam, especially in the beginner content. So much so that real useful information is nowher

I understand your point. But my contention is that there is a lot of spam, especially in the beginner content. So much so that real useful information is nowhere to be found in search engines. I have recently started learning React and when I search for a topic, I have to wade through a myriad of articles that are basically "Get Node, Get React, CRA new, etc. etc." Nothing of actual use, but search engines pick up because of SEO I guess. Finding something of value is becoming increasingly difficult. On top of that, I use DDG as my primary search engine and it doesn't help. For articles regarding PGSQL, their documentation is the ultimate source and I frankly see no reason for these articles to exist.

craigkerstiens 7y ago
I hear you on value of articles diving deeper. The Postgres docs are awesome, but I find them most valuable as reference docs once you already know how to do something. I find if you're trying to learn how to do a new thing they're not quite as useful. There is definitely some value in filling the gap between a hello world of JSON and exactly how to use a specific operator. I was gonna follow up with if there are any specific things that you might find useful on the Postgres arena would be happy to start personally writing a few, but for yourself sounds like docs are good enough :)
- kumarvvr 7y ago
  Thank you for the gesture. I love the PGSQL docs. And I usually experiment my way through the docs, as most of the time, I am usually solving a problem and will learn a bit of the underlying mechanism, quirks and tips for performance before going ahead with a method. For those, I find those docs more than sufficient. I found the same with Django docs too. The worst offender is NodeJS, and to a lesser extent, React. Edit : If only there was a method to allow users to annotate comments onto the core docs, and there was a way to upvote / downvote the comments, we could have better documentation. I have seen primitive versions of such mechanisms in PHP docs.

craigkerstiens 7y ago

I hear you on value of articles diving deeper. The Postgres docs are awesome, but I find them most valuable as reference docs once you already know how to do something. I find if you're trying to learn how to do a new thing they're not quite as useful. There is definitely some value in filling the gap between a hello world of JSON and exactly how to use a specific operator. I was gonna follow up with if there are any specific things that you might find useful on the Postgres arena would be happy to start personally writing a few, but for yourself sounds like docs are good enough :)

kumarvvr 7y ago
Thank you for the gesture. I love the PGSQL docs. And I usually experiment my way through the docs, as most of the time, I am usually solving a problem and will learn a bit of the underlying mechanism, quirks and tips for performance before going ahead with a method. For those, I find those docs more than sufficient. I found the same with Django docs too. The worst offender is NodeJS, and to a lesser extent, React. Edit : If only there was a method to allow users to annotate comments onto the core docs, and there was a way to upvote / downvote the comments, we could have better documentation. I have seen primitive versions of such mechanisms in PHP docs.