• Ooops@feddit.org
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        9 hours ago

        Low TTL of dns entries is there to avoid classical Cache Invalidation, so kind of…

      • aquovie@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 hours ago

        I keep seeing “networking is hard” come up here. Where is this coming from? Is it IPv6 or something?

        • blargh513@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          8
          ·
          10 hours ago

          I started in networks.

          The volume of people who work in technology that don’t understand networking is astonishing. I probably spent more time explaining how a web proxy works than I did actually setting things up.

          Firewall rules? Spells and magic. Routing? Unpossible! DNS? Forget it, I’m going home.

          • prettybunnys@piefed.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            6 hours ago

            Subnetting and the difference between /8 and /24 or /32 and how you allocate IP addresses between them has always been crazy for me to grasp.

            I feel like if I could finally understand that after 20 years … I’d be happy but no here I am, effectively ignorant to it and looking at networking wizards as true wizards

        • optional@sh.itjust.works
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          10 hours ago

          Networking is so easy nowadays. Just plug a network cable into your device and it mostly works out of the box. Don’t you guys remember the bad old times of coax cables and token ring?

          Imagine providing a public WiFi before 1993, even if you ignore the fact that WiFis had a cable back then.

          • Ooops@feddit.org
            link
            fedilink
            arrow-up
            2
            ·
            9 hours ago

            I’m not old enough to having been bothered by network rings and grew up with the high-tech that were end resistors.

    • who@feddit.org
      link
      fedilink
      English
      arrow-up
      5
      ·
      10 hours ago

      OP might be suffering from cache misses. (Or maybe hasn’t yet learnt about it.)

  • humanspiral@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    6 hours ago

    0 based indexing of course, so what’s the joke? oh, mixing up count and max index is a hardship you get over after a couple of years, but it comes back sometimes.

  • who@feddit.org
    link
    fedilink
    English
    arrow-up
    32
    ·
    edit-2
    9 hours ago

    There are only two hard things in Computer Science: cache invalidation and naming things.

    — Widely attributed to Phil Karlton

    There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.

    — Leon Bambrick 2010-01-01

    • queerlilhayseed@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 hours ago

      Human-human interface configuration falls under networking issues. And naming things, now that I think about it.

      And occasionally off-by-one issues :(

    • Susaga@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      10 hours ago

      It’s possible your coworkers are the ones dealing with those issues, and you just never notice.

    • queerlilhayseed@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      Off-by-one errors are real errors. A common mistake rookie developers make (or used to make, anyway) is forgetting that arrays are zero-indexed when creating an array, then seeing the value that should be in array[n-1] when they read array[n].

      Another common off-by-one error is double counting: Some accumulators don’t do all their processing in the same function, and occasionally one thing will be checked for inclusion twice, causing the accumulator to have one more element than it should.