I often find myself explaining the same things in real life and online, so I recently started writing technical blog posts.
This one is about why it was a mistake to call 1024 bytes a kilobyte. It’s about a 20min read so thank you very much in advance if you find the time to read it.
Feedback is very much welcome. Thank you.
This is a great example of how a lot of people dont read the posts they are replying to.
This is even more prevalent when arguments break out in the comments where people misunderstand each other or argue about things that one side said that they qualified later in the original comment but the other side didnt read the whole comment and instead hyperfocused on that one sentence that really garbled their goolies.
I trust that none of these people would have read the article even if they had realised it was there.
P.s. i fully agree with you. It’s a great blog post. Good write-up. Very informative. The only quibble i have is that I’ve always loved the words mebibyte, gibibyte, etc.
It’s something I’ve noticed, not just in the fediverse.
Not just me. A decline in functional literacy is something international studies have reported on. People can still read, but they’re unable to concentrate on longer articles or miss certain details.
Anecdotally, I’ve had discussions in the fediverse, where someone posts a link to an article to support their argument. So I read it, and quite often it’s obvious they either haven’t (fully) read the article or fundamentally misunderstood what it says.
It’s quite worrying. It’s like a mechanic who decides to repair a car based on the picture on the manual’s cover, but on a societal level. Can’t help but think it explains a lot of political instability.