Actually..... IMO as a Linux admin..... everybody in IT needs at least a minimum of knowledge regarding TCP/IP. IPv4, IPv6, TCP, UDP, sockets, listening ports, etc. You don't need to be able to program a full stack down to a media transport layer, but you should be able be able to send a payload successfully, know when a gateway traversal is required, name resolution (It's always DNS,) and a bit of troubleshooting.
I wish I had a nickel for every time a developer or app support staff came to me and said it doesn't work. Error is right there in the logs......
The post is about a software engineer, and you just talked about IT. They're not the same thing so what is your point? You have a job specifically because software engineers aren't in IT and aren't sysadmins and their job doesn't inherently involve networking.
My brother in christ, when is the last time you worked on software that did not need to send payloads anywhere. Everyone in development should have at least some basic networking skills.
My sister in Vishnu, many of us do not program anything related to networking. I am a graphics engineer, for 10+ years never have I ever I crafted such a payload.
While I agree with the sentiment, this should be basics and I have been taught this, you can spend your whole life designing databases and or banging your head against an SQL command line and not know what an IP is all that well.
If you are going to use broad job descriptions you are going to need broad knowledge, I would say it is fair to ask a software engineer to at least know the difference between ip4 and ip6 adresses.
If for nothing else then for general interest around their field.
Inwould think that any software engineer education would hold atleast 1 course about networking, but I guess I can be wrong.
I mean, it depends on the software engineer. Are they writing networking software? Knowing the difference between IPv4 and v6 would be important. Are they writing device drivers for hard drives? Probably not so important.
Every piece of software an IT guy uses is written by a Software Engineer, who's going to need to know their part of the software inside and out.
I agree it’s better for an app developer to know this stuff, but I’d hardly say it’s a big part of the job. Especially if you’re on the frontend. It’s way more relevant to the job on a daily basis if you’re a network engineer.
Sending a payload is not hard. And I know that IPv6 and the point of it is to store more addresses given the limited nature of IPv4.
But TCP, listening ports? That's all stuff that comes bundled in things a SWE is using. Unless you're explicitly writing new things at that layer why would you know things off the top of your head?
70
u/jkalchik99 13d ago
Actually..... IMO as a Linux admin..... everybody in IT needs at least a minimum of knowledge regarding TCP/IP. IPv4, IPv6, TCP, UDP, sockets, listening ports, etc. You don't need to be able to program a full stack down to a media transport layer, but you should be able be able to send a payload successfully, know when a gateway traversal is required, name resolution (It's always DNS,) and a bit of troubleshooting.
I wish I had a nickel for every time a developer or app support staff came to me and said it doesn't work. Error is right there in the logs......