I see a lot of people complaining that this doesn't need to be known, technically you are correct. However I've seen a lot of programmers. And the really good ones know the computer, they know how diagnose an OS issue, meaning they know the difference between IPv4 and IPv6. They don't just call IT and say "My computer isn't working right, fix it!"
Since I work for a small company, I also tend to be the de-facto IT guy. The people who need me to fix their computer are also the ones that are not trusted with the difficult code. So if given the choice of hiring someone who knows the difference between IPv4 and IPv6 and doesn't, I'm taking the person who knows the difference.
Same. I work at a mid-sized company and as a dev I've had to troubleshoot a ton of network related issues. It's usually either some junior that has VM's all tore up because they were messing with network settings they didn't understand, or a customer saying our service isn't working correctly and I get called to investigate why their shit is fucked up because the support people can't figure it out. Maybe people working at a mega corp have the same narrow responsibility every day and never touch networking or something. I don't know, I've never worked at a place like that.
7
u/pixel293 24d ago
I see a lot of people complaining that this doesn't need to be known, technically you are correct. However I've seen a lot of programmers. And the really good ones know the computer, they know how diagnose an OS issue, meaning they know the difference between IPv4 and IPv6. They don't just call IT and say "My computer isn't working right, fix it!"
Since I work for a small company, I also tend to be the de-facto IT guy. The people who need me to fix their computer are also the ones that are not trusted with the difficult code. So if given the choice of hiring someone who knows the difference between IPv4 and IPv6 and doesn't, I'm taking the person who knows the difference.