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.<p>Only when I don't fully understand the arguments then I read the article
9 out 10 times never read the article - comments often shine the light that there is a better X that is open source, or that the thing I wanted when reading the title is Mac or IOS only - save me the click and the time.<p>I do try to read the article / thing if I am going to comment - but that's not many.<p>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.
Depends. If I don't understand from the headline what it is all about I check the top comments. If the topic sounds like genuinely interesting technical information I read the article first. And everything between those 2 extremes depending on the phase of the moon...
I used to, but I'm trying not to anymore. I've seen enough instances where the top comment was either irrelevant or outright wrong about the article in question.
Often. Sometimes I don’t read the article at all because I’m more interested in the conversation happening than I am in whatever the article was about. And it’s common for HN comments to evolve into a conversation about something the article is tangential.
Based on the responses/replies here -<p>Perhaps it is time to retire one of the HN guidelines namely - Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that." since it seems a lot of people <i>haven't</i> actually RTFA when posting comments.
Yes, and I often don't read the article at all, especially if it's blogspam that can be largely inferred from the title.<p>e.g. "Why I like small projects"
I try not to. Sometimes I'm lazy but I usually try to put in the effort to read the article first, if I think it might be interesting, because I tend to find the articles to be more insightful than the commentariat, and because I tend to complain about people not reading the articles a lot. I think it's important to try to expand one's intellectual horizons and take the risk of engagement in a community predicated on satisfying intellectual curiosity, because otherwise comments tend to feed on each others' ignorance rather than spread insight. Especially for subjects not likely to be in HN's wheelhouse (anything non-technical, or technical but not related to programming) or subjects with any political or social dimension, where the tendency towards the "aggressively ignorant hot take" might prevail. I see little value in reading the comments first in those cases.<p>Conversely, if I <i>haven't</i> read the article, I try not to comment as if I have.
Not usually, but sometimes I will read part of an article and then look to the comments to see if there is an explanation or discussion of something I didn't understand, before continuing. I would not trust HN comment threads to replace the content of articles: I'm fairly certain there are a lot of people who don't read the articles before <i>commenting</i> on them.
I read mostly only the comments except the:
"why not that other irrelevant thing", "I remember this irrelevant anecdote", "Rust ftw"<p>For science postings I read the artcle, half of wikipedia and then humbly read the comments.
I rarely read articles. Reading an article is a time commitment of, usually, at least several minutes. But I can skim through the comments without commitment.<p>And often the first few comments are enough for me to decide if the article is worth reading.
I usually don't. I don't want the comments to color my thinking on the article.<p>The 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.
If the title looks like clickbait or overly US political, I'll skim the top few comments first to see if there's any interesting conversations. If not, there's a decent chance that the article is also pants so I won't bother with either the article or the comments.
It depends. When commenting I read the article first but often times I'm more interested in the discussion, other people's opinions, and further interesting related content linked in the comments.
Depends on the topic, even if HN has a relatively high signal to noise ratio, a lot of it is still noise. I mostly read blogs off gemini aggregators like Antenna.<p>So I'm mostly using HN as an ersatz message board.
Never thought of doing that. Usually for articles I do not read the comments at all. And I only look at the article if I have a STRONG interest. But NOW I have a new tactic, thanks.
I almost always read the comments before reading the article (and sometimes don't read the article at all).<p>I do, however, read the article before I <i>write</i> a comment of my own.
It depends on type of article. If that is some story I prefer to read it. If that is some kind of news, I prefer comments. If that is about idea, I prefer both.
I certainly VISIT the comments first. That way I can just use the back button to get back to the comments after I read it. Which I don't always do.
I just come here to read discussions. I learn so much just from random people mentioning stuff like "hey I use X and it's really great for Y, much better than Z". I don't care much for the articles themselves, especially if they come from a website whose sole purpose is "writing articles", has paywalls or advertisements, or is terribly designed or implemented with a crapload of JavaScript code whose execution is needed just to show a simple paragraph of text.<p>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.
usually. Depends on how much I care about the article. If it is squarely relevant to my interests, I click to it directly. Otherwise, the HN commentary is often more enlightening (or at least amusing).