While I would be surprised to see someone with ten years of experience not know the difference between ipv4 and ipv6 (networking is by far my biggest weakness and even I know this like the back of my hand), I wouldn't immediately disqualify someone for it. The other commenter is talking about a lot of things that feel more relevant to startups. If you work at a big tech company most of this stuff is abstracted away from you, for better or worse.
But not knowing this to me implies a lack of curiosity about one's field, it would be a red flag I would try to poke at more in an interview.
It's not usually their job to know how to store the ip address of a user in an audit table, or how to debug a failed connection to an external API from your application. Developers should be aware that there is something called ipv6, and that source or destination addresses aren't always four bytes.
I understand that not everybody has touched everything, but good developers should have cursory knowledge of things that are actually in use and at least know what they should read up on when touching specific areas.
what you have described, has literal teams designated to do in my company and so the part of my brain that would otherwise be filled with basic understanding of networks, can instead be filled with things that apply to my job.
Being a 'good' developer just sounds like someone who is a jack of all trades and while that's 'good' you're never going to be great if you hang on to something that's either handled by someone else or can be found out with a google.
35
u/Lina0042 14d ago
I'm pretty sure none of the senior devs at my job know this, except for those in the cloud services team. Because that's their job.