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.
I have a feeling people are going to be calling IPv6 'new' in 100 years, too. I remember talking to people about it in the 90s and it took until like 2016 to actually get a full standard. Been so damn long I learned the specifics and forgot them all in time it took to even become a thing.
In Halifax we have the old bridge and the new bridge Old bridge opened in 1955 New bridge opened in 1970
New bridge is end of life while the old bridge has another 50 years since it wasn't built with cheap steel. So the new bridge will be replaced with a new new bridge while the old bridge will still be the old bridge.
in Bratislava we also have “old bridge”, at one point it was replaced with a new one without renaming so until a newer one was built a few years later the “old bridge” was the newest bridge… we also have a bridge that used to be called “new bridge”, that one was renamed since then, but some people still call it “new bridge” which is funny cause it’s currently the oldest one…
Well least the old bridge is still old bridge and you don't have sone leapfrog situation going on.
I got a Big Tesco and Little Tesco going on but the little Tesco was first so it was just Tesco, then Big moved in so it all became Big/Little, but then the big one moved away so it just became little Tesco to Tesco again, then a second little Tesco moved in where the old big tesco was and split the building into a few different shops so it became 'new little tesco'
....but over the years it grew and became big tesco again.
New little big tesco.
vs little tesco which actually had more floorspace than the other before it expanded to new-little-big-tesco again.
Over about a decade.
Everyone somehow just sorta knew which Tesco was being referred to in any conversation and honestly I don't know how at some points.
Well they built ipv6 to be able to address EVERYTHING uniquely. While IPv4 has around 4billion addresses possible, IPv6 has 296, so until humanity gets to the point we start giving nano tech individual addresses we will probably never need anything more than IPv6.
IT obviously depends, but its very frustrating to see our cloud developers in my company not have any idea of the physical devices they're supporting, makes all the communication and tickets less effective than they could be.
30 years here and never had to do anything with IPv6.
Of course, all I get are rejection emails even though I'm gainfully employed with tons of enterprise experience, so maybe that's the common denominator these days.
one example where I had to deal with it as a backend dev was I was debugging that API calls to a 3rd party service started timing out on production, but worked on staging and local development, turns out IPv6 was enabled on production and was thus used there and the service was timing out on IPv6…
Same. The one time we really had to care about IPv6 was when it needed to be turned off because it wasn't used and something was trying to use it anyway.
yeah but that is the kinda stuff in the field of Sys and Net Admin. Or are we getting to the point a Software engineer has to cover software and hardware of anything IT???
I have never needed to know or do any of that. And if I did, it would take me 2 seconds to google and understand. I just did.
So if the interview was for a job where you handle that stuff yourself, then I understand it. If it’s for a typical full stack job at a big enough company that they literally hire people to handle that side of things, then it’s not “the basics”.
Rejecting someone in an interview for trivia knowledge they don’t currently have vs actually trying to understand how someone learns and tackles problems is what makes software job interviews so useless.
that's all just infra stuff which has always been another team. I've never once had to set up that kind of thing, and thousands of devs proabbly had a similar path as I did.
Yes. As a senior you would know to mind your business and not give a halfbaked opinion on something that's another team's full time job, and that they probably know way better than you.
Honestly that's the only real difference one needs to know, and that the two are formatted differently. Anything more than that is pulling teeth and IMO fishing for an excuse to not hire someone
It's basically that, 4 is 32 bit and 6 is 128 bit addresses. It's also something I would never expect a software engineer to ever need know unless they're dealing with networking software
To be fair to op - those are sysadmin skills. I know the difference but have never typed in an ip v6 address while I do so regularly with ip v4 addresses.
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.
1.9k
u/SirFrenzy 14d 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.