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.

  • wischi@programming.devOP
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    17
    ·
    11 months ago

    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.

    • logicbomb@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      2
      ·
      11 months ago

      I don’t benefit if you read it.

      You don’t benefit financially, but there are other benefits. For example, you specifically asked for feedback, and you have received some.

      • wischi@programming.devOP
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        17
        ·
        11 months ago

        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.