my view on this is based on my work in IT, I work in capacity that means I put in new infrastructure. - this is what I think.
no. - programming is not the "only" CS job that will survive.
let look at this simply.
non-coding IT jobs I assume to mean IT support and consultancy.
Whilst AI systems can answer help desk calls, they may have trouble understanding how non technical people describe issues, - so help desk jobs will still be available.
a machine won't be installing servers in small coms room cupboards any time soon, nor upgrading RAM in servers.
and for all devices, before you can use auto provisioning tools you have to do some wort of basic setup.
(ok if you're only buying cloud services you may never actually see a computer, but Amazon are still going to have jobs!)
but here is the real issue.
whilst these jobs will survive, they will be harder to get.
why?
well, consider that today I can use ancible to push configuration to a thousand devices, (lets say I have a new management server so I'm adding a new ACL on a switch.)
it's a small change, but i'd have taken ten minutes per device to connect,
that's basically ten 8 hour working days...
Now I can do that all inside an hour, including all change control necessary!
So I'm some hundred times more productive, the place I work don;t need to employ so many people...
also, not only will there be less jobs available, but they are going to be harder to get into.
most people don't suddenly jump into some sort of high skilled job (even those straight out of universities) but (for the western hemisphere at least) it's harder to get those entry level jobs that give you experience, and once those entry level jobs are mostly replaced with robotic systems... it's going to be harder still!
Here is the thing.
Even with infrastructure as code, (where you can use tools like cloud formation to get loads of servers spun up at once.) you're still an infrastructure worker, not a coder (though you need to know code).
the idea that only programming will survive is basically a rumor that seems to have been put about by self important programmers who think that they have no need for infrastructure specialists because they can make servers or something (if seen how that ends, and it's often not well!)
I can't see programmers and coders fairing much better that infrastructure people either; there is now an awful lot of code automation. auto test etc...
jobs won't completely disappear, thy'll just but a bit harder to get.
no. - programming is not the "only" CS job that will survive.
let look at this simply.
non-coding IT jobs I assume to mean IT support and consultancy.
Whilst AI systems can answer help desk calls, they may have trouble understanding how non technical people describe issues, - so help desk jobs will still be available.
a machine won't be installing servers in small coms room cupboards any time soon, nor upgrading RAM in servers.
and for all devices, before you can use auto provisioning tools you have to do some wort of basic setup.
(ok if you're only buying cloud services you may never actually see a computer, but Amazon are still going to have jobs!)
but here is the real issue.
whilst these jobs will survive, they will be harder to get.
why?
well, consider that today I can use ancible to push configuration to a thousand devices, (lets say I have a new management server so I'm adding a new ACL on a switch.)
it's a small change, but i'd have taken ten minutes per device to connect,
that's basically ten 8 hour working days...
Now I can do that all inside an hour, including all change control necessary!
So I'm some hundred times more productive, the place I work don;t need to employ so many people...
also, not only will there be less jobs available, but they are going to be harder to get into.
most people don't suddenly jump into some sort of high skilled job (even those straight out of universities) but (for the western hemisphere at least) it's harder to get those entry level jobs that give you experience, and once those entry level jobs are mostly replaced with robotic systems... it's going to be harder still!
Here is the thing.
Even with infrastructure as code, (where you can use tools like cloud formation to get loads of servers spun up at once.) you're still an infrastructure worker, not a coder (though you need to know code).
the idea that only programming will survive is basically a rumor that seems to have been put about by self important programmers who think that they have no need for infrastructure specialists because they can make servers or something (if seen how that ends, and it's often not well!)
I can't see programmers and coders fairing much better that infrastructure people either; there is now an awful lot of code automation. auto test etc...
jobs won't completely disappear, thy'll just but a bit harder to get.
