Earlier quoted context omitted.
This drives me a bit nutty tbh. I dont feel like getting into it at the moment, because the entire subject deserves a proper gothrough.
Why? One "sysadmin" who can write software can manage far more machines than one who can't. Source: started my career as a Solaris Sysadmin with a CS degree.
For one, because many sysadmins don't have the proper CS background to "program" well. We get shit done, mostly in bash/perl/python, (these days maybe in go, etc), but devs who read sysadmin code tend to gasp and sigh a lot.
Two, being a sysadmin is more than just admining the machines. A senior has to be just as comfortable in a suit in a meeting with the C-suite, writing reports, doing BCPs etc, as they are terminating cable.
Three, coding is useless if you don't know how to fix issues, or diagnose them in order to know what the issue is that needs fixing in the first place.
Four, this push to sysadmins must code seems to largely be a filter-bubble effect of companies that are software focused. Thousands of sysadmins across the world are supporting companies that don't even have a dev team, so the whole "sysadmin is dying, devops is the future" angle is naive imho.
Five, does writing config files in something like ansible yaml or hashicorp config language really count as coding? Because ok then I'm down with all sysadmins must code. But far too often I've seen some poor sysadmin tossed a mess of python and told to fix it... and then when they struggle they hear heaps of criticism. Don't even get me started on all the huge perl messes from "sysadmins who coded" I've had to clean up...
Do you see the general gist of where I am going on this? Did you evolve into a software engineer, or did you move up to more managerial position of senior or CTO/CIO? One thing to keep in mind is that many companies don't have a CTO or CIO, and sometimes don't even have IT department heads other than a senior sysadmin. Much of the pain points we are talking about are probably different in different company cultures, and are more situation specific. What I've found is that managers tend to think that if their sysadmin can code that means their sysadmin is a dev, and they can save money by having them fill both roles, and that almost never turns out well for anyone.