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.
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.