this post was submitted on 27 Dec 2023
144 points (69.4% liked)
Technology
59329 readers
6779 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I also assume that people are answering that way because they thought it was a question.
However, it's also possible that they saw it described as a 20 minute read, and knew that the answer actually takes about 10 seconds to read, and figured that they'd save people 19 minutes and 50 seconds.
Bit of a tangent and anecdotal, but I went back in to higher education a few years ago. I'm middle-aged, I was surrounded by younger people. We're asked to read an article, everyone starts reading. I read it through, underline the important bits, I'm done reading. I look around. Everyone's still reading. Oh well, they'll be done soon. Nope. I think it took most of them 15 minutes to read an article I'd read in under 5. I was a bit perplexed. This is higher education, these aren't idiots, these are people who should be able to read articles quickly.
There are plenty of reports of functional literacy decreasing. That children are slower at reading and are less able to understand what they've read. Anecdotally, it seems like younger generations really aren't used to reading longer articles anymore. I grew up reading books as a kid. That's what we did before phones and the internet. I wonder if younger generations simply don't have that much experience reading, which is why it takes them so long to read, which is why they read even less.
In the case of this article, they see 20 minutes, they're scared off. So they simply guess what was in the article. That's pretty worrying if that's what people do. If you're unable or unwilling to read longer stuff, you're likely to make ill informed choices or be more easily influenced.
TLDR: old person went back to school and reads faster than younger people, thinks younger people don't know how to read quickly.
Bit ironic that you don't seem to have read my comment properly.
Firstly, you missed the caveat about the example used being anecdotal.
Then you seem to have missed the bit about reports suggesting functional literacy is decreasing.
A quick google:
https://hechingerreport.org/americas-reading-problem-scores-were-dropping-even-before-the-pandemic/
https://hechingerreport.org/proof-points-why-reading-comprehension-is-deteriorating/
That's the joke, but ok.
I'm middle-aged and read slowly. Explain that, asshole.
Ok boomer.
I'm not "scared off". I'm on Lemmy to have discussions, not to read articles. If I want to read articles I'll get a magazine.
Wait, you're on a link aggregator platform and not interested in the links?
It's true that the actual "story" is very short. 1 kB is 1000 bytes and 1 KiB is 1024 bytes. But the post is not about this, but about why calling 1024 a kilobyte always was wrong even in a historical context and even though almost everybody did that.
Yes. But it does raise the question of why you didn't say that in either your title:
or your description:
The title and description were your two chances to convince people to read your article. But what they say is that it's a 20 minute read for 10 seconds of information. There is nothing that says there will be historical context.
I get that you might want to make the title more clickbaitey, but why write a description out if you're not going to tell what's actually in the article?
So, that's my feedback. I hope this helps.
One other bit of closely-related feedback, for your writing, in general. Always start with the most important part. Assume that people will stop reading unless you convince them otherwise. Your title should convince people to read the article, or at least to read the description. The very first part of your description is your chance to convince people to click through to the article, but you used it to tell an anecdote about why you wrote the article.
I'm the kind of person who often reads articles all the way through, but I have discovered that most people lose interest quickly and will stop reading.
I tried to make the title the exact opposite of clickbait. There are no unanswered questions on purpose. No "Find out if a kilobyte is 1024 bytes or 1000 bytes". I think people are smart enough that I not just reiterate for 20min why a kilobyte is 1000 bytes but instead go into more details.
The main problem is probably that people won't sacrifice 20min of there time on something they are not sure if it's a good read but the only thing I can do is trying to encourage them to read it anyway.
There are not ads, no tracking, no cookies, no login, no newsletter, no paywall. I don't benefit if you read it. I'd like to clear up misconceptions but I can't force people to read it.
You don't benefit financially, but there are other benefits. For example, you specifically asked for feedback, and you have received some.
I don't get feedback just because you read it. I'm thankful for feedback but my sentence was accurate. I don't benefit if you read it.
Every part of your comment has something factually wrong or fallacious.
My reading the part I am giving feedback on is a prerequisite for actually giving feedback. I am obviously a person who graciously responded to your request, not somebody that you somehow ordered to give feedback. I don't know what you think you gain from viewing it this way.
I didn't say it was inaccurate, but that it didn't tell people why to read the article. You didn't ask me to tell you inaccuracies. You asked for "feedback". You also don't seem to be thankful, because if you were thankful, you'd simply accept the feedback instead of throwing up straw-man arguments.
You have exactly repeated your previous statement that I already proved wrong.
I will offer you one last piece of feedback. Just stop arguing. You can never look gracious pursuing an argument where you ask for advice and then argue with people who took time out of their day to help you.
Upvotes and downvotes don't determine whether people are factually right, but they do help you gauge what people think when they read your comments, and what I'm seeing is that you're not ingratiating yourself to the people who you are asking to read your article. Even if you could win this argument, and you can't, you wouldn't want to, because you'd look bad in doing so. When you ask for feedback, and feedback is given, just graciously accept it. If it's bad feedback, then just ignore it.
But that's also a simple answer: kilo is a metric prefix that means 1000, so kilobyte means 1000 bytes. The historical context is the history of the metric system, which is much older than modern computers.