Ask HN: I read comments before the article, do you?
I find myself reading the comments on HN before the articles most of the time...
It usually brings a better/shorter description and decent reaction.
Only when I don't fully understand the arguments then I read the article
54 comments
[ 4.4 ms ] story [ 122 ms ] threadThe exceptions arise when I have already read up on the topic, so I might read the comments to see how the article effects others, then go read it to see what slant it has.
e.g. "Why I like small projects"
I do try to read the article / thing if I am going to comment - but that's not many.
Many times the comments let me know that other needed thing is not released yet - or that no pricing info is published - love those saved clicks.
The articles have a filter that someone has gone to the "effort" of writing up an article, and it takes a lot of upvotes to get to the front page. The commentary has no such filter.
It's very easy to shoot down ideas on HN in the comments and get rewarded for it, especially if it's to dismiss a product with alternatives. Not just the now notorious dropbox comment, but I'm often seeing comments here suggesting alternatives that if you're in the know you'll realise just don't solve the problems in a pain free way.
when people mention mac only (big thanks to those who do this!) - I tend to just believe and move on.
with some projects I open tabs for the article and all the alternatives people mention bookmark to dig into later.
So my methods are not always this or that - but as a general 'way of HN' for me, these methods are what makes HN a great time saver in general, but not always.
I also do that. Most non-news articles aren't better than the average two paragraphs HN comment, but they are 10 times as long. Time is precious and at some point who has the time for yet another "[strong opinion about some technology/pattern/that's how we do at our company]". Almost 100% of the time the comments contain better information on the topic tackled by the article and with higher information density.
If it's a news article there's always a few comments quoting important parts of the article which is usually enough to understand what's being reported.
The articles that I tend to prefer and to read are the ones that highlight a feature that I wasn't aware of about a language that I'm interested in.
I do, however, read the article before I write a comment of my own.
Occasionally, I find an interesting article and actually read it, but most of the time such articles come from personal blogs of developers who just wanna write about an interesting thing they learned. Coincidentally, such writers tend to share my love for simplicity and terseness - they contain no ads, no distractions and in most cases no necessary JavaScript code - they just write about the thing they're writing about and don't distract you. The j3s.sh website is a nice example that I could find amongst my bookmarks.
Conversely, if I haven't read the article, I try not to comment as if I have.
So I'm mostly using HN as an ersatz message board.
https://www.urbandictionary.com/define.php?term=RTFA