• Zephyr@sh.itjust.works
    link
    fedilink
    arrow-up
    26
    arrow-down
    1
    ·
    7 hours ago

    How the internet works would be more so an IT thing than a backend developer thing at least on a high level. Setting up a database doesn’t mean one knows networking well in the same way they probably don’t know cpu logic gate design well.

    • Gregers@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      2 hours ago

      You don’t need to know all the details, but I think you should understand the basic network concepts way before starting your first job as a developer

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

        At least TCP/IP, DNS, and similar things, yeah. Maybe not so much the intricate details of the wifi6 or Bluetooth protocols.

    • rumschlumpel@feddit.org
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      6 hours ago

      Arguably an engineering (hardware) or systems programming issue, too. How many IT people (even the highly competent ones) could design a router, wifi chip etc.? Or know in detail what’s going on in an internet exchange point?

      • Zephyr@sh.itjust.works
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        6 hours ago

        True and how many of those guys are well versed in fiber optics at IXPs. Maybe with like 20 dudes you could get an extremely in-depth snapshot of how the internet works from transistors to transformers and everything in-between.