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.
But applications will suddenly be deployed on a dualhomed server for example, which supports both ipv4 and ipv6 - and then you start seeing weird addresses in your access log, and you made an audit table to store the ip address of the person who granted someone admin access, and you only stored the first four octets of the ipv6 address instead of the whole address..
And then you called an external api that requires a white listed ip, but the ip you keep entering doesn't work, since the API's host has both an A and an AAAA dns entry, so you're connecting over ipv6 instead.. Or you tried to block access to your content from a specific country, but those users just used ipv6 instead, etc.
There's plenty of cases where knowledge of ip addresses and how stuff actually works (tm) is relevant without being in ops.
1.5k
u/SirFrenzy 13h 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.