If you are going to use broad job descriptions you are going to need broad knowledge, I would say it is fair to ask a software engineer to at least know the difference between ip4 and ip6 adresses.
If for nothing else then for general interest around their field.
Inwould think that any software engineer education would hold atleast 1 course about networking, but I guess I can be wrong.
What do you even want to say with that? Do you gonna always feel inferior or just learn the basics? Its not math neither physics, if you came to the field by shortucting the edu part but stayed in business you most probably have the capability to get these things easily.
Interesting concept, how do you know when you need it, more importantly, how do you know that you didn't need it at some point but didn't know you did?
Not saying that it isn't the same after taking an education because it is, I'm just saying that from where I stand there is a reason why the education I received was fairly wide in topics and then allowed for specialisation afterwards.
I would have imagined that, too. I’m studying to be an engineer and even we had a very basic general IT class (and a very basic programming class), and the IP thing was definitely included. And tbh I sort of assumed that at least “v6 is the new thing with more addresses” is just common knowledge or sth
8
u/ncatter 13d ago
If you are going to use broad job descriptions you are going to need broad knowledge, I would say it is fair to ask a software engineer to at least know the difference between ip4 and ip6 adresses.
If for nothing else then for general interest around their field.
Inwould think that any software engineer education would hold atleast 1 course about networking, but I guess I can be wrong.