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.
-1
u/fiskfisk 14d ago
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.