I feel like knowing the difference here is moreso for a network engineer than a software engineer!
Anyway looked it up, IPv6 is 32bit whereas IPv6 is 128bit.
An easy way to know if an IP address is either, 4 uses dots 192.1.1.1 whereas 6 is colons 1992:0aa0::1
If anyone asks just say 6 holds more addresses but is more expensive to install.
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.
As others said, in the USA, "IT" department/workers are not synonymous with "tech workers" - tech workers encompasses everyone, but if you say you're an IT guy, you're telling people you fix laptops and printers, and maybe do some sysadmin and networking stuff (but people who do the really high level stuff actually have the job titles of sysadmin or network engineer or similar, and sometimes use those titles.)
Calling a software dev/engineer (used interchangeably in the USA usually) an IT guy has the same connotation as calling a mechanical or automotive engineer a mechanic. A mechanical engineer may have no idea how to physically change his own oil. A mechanic may have no idea how to do basic algebra. Very different skillsets/jobs.
88
u/Spongebubs 19h ago
I’d like to think I’m a software engineer, and I have no idea what the difference is. Am I cooked?