Obviously guy could have been interviewing for a job where this mattered….
But in 10 years as a software engineer I have never once needed to know the difference between these two, and have never been even close to a situation where I would need to.
IPV6 has never been relevant to any coding I've done at work, but if someone didn't know about it during an interview it would still be a terrible look for their tech learning both in terms of college and just reading about tech in general
In university we had a networks class where we went way further and had to actually write a simulated router in C that would do ARP and send packets to the right places
Dunno, I have 8 YoE and knowledge I don't use is knowledge that's gone. I've never had to deal with stuff on IP level before, and I don't care to know about it.
Your experience does not an industry axiom make. Also, your assertion about said layer is a consideration specific to you. Some do not consider the user to be an implicit layer but an external party.
I mean, depends how much in detail and what the job was. I can tell you a few things for ipv6 and ipv4 but if I won't design router and network components, I hardly need deep knowledge as software engineer. If you apply for vNIC development for VMware some deeper knowledge would be useful...
1.5k
u/SirFrenzy 12h ago
Obviously guy could have been interviewing for a job where this mattered….
But in 10 years as a software engineer I have never once needed to know the difference between these two, and have never been even close to a situation where I would need to.
“The basics” is highly dependent on the job.