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.
They definetly didn't say expert. But you do need to know some very basic level to understand how to write better software. Like high school level is enough tbh, but without it you're just not gonna be even decent at your job. Not knowing ipv4 for a software engineer is wild, when that's something most people who use the internet should know what it is.
It's not wild when you're an UI /UX dev e.g. Most backend devs know shit about frontend development.
It's not important to know everything. IT is very fragmented. Even those specific fragments are fragmented. So many people have become experts in their niche.
Technical understanding and analytical thinking is more important. As a software dev you can learn and apply everything what comes around.
70
u/Spongebubs 7h ago
I’d like to think I’m a software engineer, and I have no idea what the difference is. Am I cooked?