this post was submitted on 13 Jul 2026
372 points (99.7% liked)
Greentext
8491 readers
571 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
At least TCP/IP, DNS, and similar things, yeah. Maybe not so much the intricate details of the wifi6 or Bluetooth protocols.
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?
Some developers that know both networking and developing will make those chips, the avarage developer will know about TCP/IP, DNS and those basics, at max
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.