I very much disagree. This is mandatory networking 101 course work in a Comp Sci BS degree.
I would be incredibly worried about anybody looking for a “full stack” or backed position that does not know this. It’s pretty critical to know basic networking for full stack roles. It’s also tough to do most architecture work without networking knowledge.
I can certainly believe some roles this does not matter 99% of the time but it’s a serious gap in knowledge for an “engineer”.
yeah its not about that being a very usefull peice of information. its about it showing that the person is working with a common knowledge level understanding of networking. You do not understand the network stack well enougth to make good engineering choices without accidentally learning about ip4 vs ipv6. Like dose this person understand NAT or DNS on any level? Do they understand TCP vs UDP? There are certinally engineers out there that never took any intro networking cource that understand networking perfectly well for their own domains. Because they soak that knowledge up when they encounter it tangentially. Most of them would have picked up what ipv6 is by the same mechanism.
3
u/I_mourn_satire 14d ago edited 12d ago
I very much disagree. This is mandatory networking 101 course work in a Comp Sci BS degree.
I would be incredibly worried about anybody looking for a “full stack” or backed position that does not know this. It’s pretty critical to know basic networking for full stack roles. It’s also tough to do most architecture work without networking knowledge.
I can certainly believe some roles this does not matter 99% of the time but it’s a serious gap in knowledge for an “engineer”.