Try to keep it practical (like something that would not be fairly doable, you just havent gotten around to it…yet)

  • vaionko@sopuli.xyz
    link
    fedilink
    arrow-up
    6
    ·
    8 hours ago

    Converting between hexadecimal and binary. It’s not that hard and it would’ve been useful many times, but I still haven’t memorised it

    • TootSweet@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      If your a software engineer, memorizing an ASCII table (particularly the hex numbers of each character code) is definitely helpful. If for no other reason than so that you can read things that are randomly written in binary without having to consult a table.

      Something not really otherwise terribly useful that nonetheless helped me keep my sanity: learn how to convert to base64 in your head. At work, we had really boring 8-hours-a-day training for a couple of weeks. To pass the time, I came up with random strings to base64 encode in my head. “Hat is 48 61 7a. The first six bits are 010010 which in base64 is an S. The next six bits would be 000110 which in base64 is G.” Etc. I’d write down the base64 strings character by character as I derived them and then check my results for errors when I got back to my desk.

      • CarrotsHaveEars@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        7 hours ago

        It’s not something you try to recite. You just do it so many times you became too good at it to look at the table.

        Four bits can represent up to 15, from 0000 to 1111. Correspondingly, 0 to F in hex.

        Binary from right to left is 1, 2, 4, 8.

        One byte is eight bits. It takes eight digit places.
        XXXX XXXX

        0000 0000 to 1111 1111
        00 to FF
        0 to 255