FWIW the headline was more persuasive than the article, which draws an odd analogy between open source (trustworthy without auditing the code due to being audited by many other people) and news (not always trustworthy despite being audited by many people) and bafflingly concludes that the reason that people can't faithfully discern what happened with 99% certainty by reading a broad range of headlines is due to censorship.
Perhaps the author's experience of the real world is based entirely on reading headlines.
Perhaps he should read a full article about the bystander effect. I wonder how many people actually audit open source code (or even take any action further than just not using it if they find something odd).
I tried to skim this but it’s full of such lofty language (“one should…”) and wordy prose that I couldn’t make heads or tails as to what the actual point was. Sure, I went to college, but you don’t need to put a ten letter word in every single sentence…
I tried to actually read it beyond skimming, and the problem isn't just that it's full of "lofty language"; I can deal with that. It's just that a lot of it doesn't seem to make a lot of sense.
"Should information be liberated and organized, the full audit of scientific studies will only be necessary for those looking to progress from ninety-seven to ninety-nine percent certainty - and their work doing be more plainly and compactly communicated."
What does that even mean? And in full context it's not any clearer.
I got strong Stuart Pearson vibes with this one.
I guess a lot of people are voting and commenting on the headline alone, as is common. But I have no idea what point the author was trying to make.
Damn, I got beaten to the "I only read the headline" comment.
I did read the article though, and I found it a bit confusing. Assuming it is written in good faith by a real person, my concern is that the central analogy to open source software does not hold up.
Someone who runs OSS after gaining trust through the headline-like "shortcut" verification process that the author describes gains utility through the execution of the software, not through the shortcut verification of it.
In contrast, when reading the news, the ideal shortcut form that the author dreams of (i.e. being able to just read the headline) seems to be skipping the primary utility of the content itself.
In other words, I don't think reading the news should be about trying to consume as many factoids as possible. Better to read a few good articles than get a one-sentence-deep summary of everything that happened everywhere.
That's a great idea. A neutral 3rd party re-writing headlines.
I think that bad headlines are one of the biggest problems in journalism today. I have seen articles posted on social media by people who obviously only read the headline. And when I actually read the headline, the article content is almost completely contradictory to the headline. My understanding is that editors usually write the headlines. They may be the real problem as many of the journalists are doing a pretty good job.
Headlines are too short to inform. There's almost always context and nuance that's just as important as whatever the headline is about. Even the full article often fails to go in enough depth on this, and it's pretty much impossible to summarize that in the headline unless you make it a "headparagraph".
If you've been following the news, a headline is often sufficient. The total ongoing story takes up many books, but the differential between yesterday and today is often quite small.
And if you haven't been following it, no newspaper article is going to fill you in on the background. As I said, that's books worth of material.
They often try to split the difference, with mixed results. Sometimes it works. Sometimes it just fills the space with vapid, pointless noise -- quotes from irrelevant people, oversimplifications, ludicrous extrapolations, etc. In the worst case that infects the headline, and what could have been one sentence worth of genuine knowledge becomes worse than nothing.
My hunch is the author has more experience with tweets than articles - tweets in crypto communities often comprise a single run-on sentence packed with keywords and (counter-cultural) intelligence-signaling.
I am always reminded of this Thoreau quote when we talk about people reading only headlines, or titles.
“And I am sure that I never read any memorable news in a newspaper. If we read of one man robbed, or murdered, or killed by accident, or one house burned, or one vessel wrecked, or one steamboat blown up, or one cow run over on the Western Railroad, or one mad dog killed, or one lot of grasshoppers in the winter -- we never need read of another. One is enough. If you are acquainted with the principle, what do you care for a myriad instances and applications? To a philosopher all news, as it is called, is gossip, and they who edit and read it are old women over their tea.”
> And so describes most users experience with open source software. The exposure of its inner workings is not a direct benefit to most users - it simply makes undesired and unexpected behaviors detectable and unsustainable. This is not wholly unlike the common media consumer's desire to truncate what information they need to consume to reach conclusions.
Arguing by analogy is dangerous, in this case because doing a code review of open source software is actually not like reading a news article, or being an informed citizen. The incentives are different in each case, so is the actual activity, so are the people involved, so is the level of expertise required, so is the social obligation. It's actually only really alike in a couple ways, the biggest one being: you're looking at something. Okay.
> Strong, but basic critical thinking, not among all, but spread among enough, is sufficient to collectively process information. It is the faux authority of censorship which causes such a practice to appear unreliable.
In the U.S., the first amendment exists, in part, because we need voters who engage vigorously with the world of ideas. Compulsory liberal education exists to prepare people with the skills to do so. No such obligation exists for code reviews, which is just one reason why this is a bad analogy.
And yeah, you "should" be able to get away with just reading headlines, but in practice what happens? You get an ignorant, disengaged population that sees the world through the eyes of the people who (in essence) write headlines for people who only read headlines. The solution is probably not to say "oh, we just need better headline", it's for people to increase their critical reading skills and their engagement with information that is (to step into the dangerous world of software analogies) 'closer to the metal'.
23 comments
[ 2.5 ms ] story [ 61.0 ms ] threadI’m going to go check now.
Perhaps the author's experience of the real world is based entirely on reading headlines.
We should probably read neither.
"Should information be liberated and organized, the full audit of scientific studies will only be necessary for those looking to progress from ninety-seven to ninety-nine percent certainty - and their work doing be more plainly and compactly communicated."
What does that even mean? And in full context it's not any clearer.
I got strong Stuart Pearson vibes with this one.
I guess a lot of people are voting and commenting on the headline alone, as is common. But I have no idea what point the author was trying to make.
I did read the article though, and I found it a bit confusing. Assuming it is written in good faith by a real person, my concern is that the central analogy to open source software does not hold up.
Someone who runs OSS after gaining trust through the headline-like "shortcut" verification process that the author describes gains utility through the execution of the software, not through the shortcut verification of it.
In contrast, when reading the news, the ideal shortcut form that the author dreams of (i.e. being able to just read the headline) seems to be skipping the primary utility of the content itself.
In other words, I don't think reading the news should be about trying to consume as many factoids as possible. Better to read a few good articles than get a one-sentence-deep summary of everything that happened everywhere.
Idea: ChatGPT chrome extension that replaces the headline with one generated from the actual article.
I think that bad headlines are one of the biggest problems in journalism today. I have seen articles posted on social media by people who obviously only read the headline. And when I actually read the headline, the article content is almost completely contradictory to the headline. My understanding is that editors usually write the headlines. They may be the real problem as many of the journalists are doing a pretty good job.
And if you haven't been following it, no newspaper article is going to fill you in on the background. As I said, that's books worth of material.
They often try to split the difference, with mixed results. Sometimes it works. Sometimes it just fills the space with vapid, pointless noise -- quotes from irrelevant people, oversimplifications, ludicrous extrapolations, etc. In the worst case that infects the headline, and what could have been one sentence worth of genuine knowledge becomes worse than nothing.
“And I am sure that I never read any memorable news in a newspaper. If we read of one man robbed, or murdered, or killed by accident, or one house burned, or one vessel wrecked, or one steamboat blown up, or one cow run over on the Western Railroad, or one mad dog killed, or one lot of grasshoppers in the winter -- we never need read of another. One is enough. If you are acquainted with the principle, what do you care for a myriad instances and applications? To a philosopher all news, as it is called, is gossip, and they who edit and read it are old women over their tea.”
Arguing by analogy is dangerous, in this case because doing a code review of open source software is actually not like reading a news article, or being an informed citizen. The incentives are different in each case, so is the actual activity, so are the people involved, so is the level of expertise required, so is the social obligation. It's actually only really alike in a couple ways, the biggest one being: you're looking at something. Okay.
> Strong, but basic critical thinking, not among all, but spread among enough, is sufficient to collectively process information. It is the faux authority of censorship which causes such a practice to appear unreliable.
In the U.S., the first amendment exists, in part, because we need voters who engage vigorously with the world of ideas. Compulsory liberal education exists to prepare people with the skills to do so. No such obligation exists for code reviews, which is just one reason why this is a bad analogy.
And yeah, you "should" be able to get away with just reading headlines, but in practice what happens? You get an ignorant, disengaged population that sees the world through the eyes of the people who (in essence) write headlines for people who only read headlines. The solution is probably not to say "oh, we just need better headline", it's for people to increase their critical reading skills and their engagement with information that is (to step into the dangerous world of software analogies) 'closer to the metal'.