If you keep it small-scale, I guess. But, sooner or later unless you work in one of those finger-paint kits like checkpoint, you’re going to need to write some terraform, chef or - fuck no - Ansible. The latter is less code than codes, or perhaps a suicide note, but it’s still out there.
Hell; my boss, leading a team in an org so big and old that it’s got a dedicated AIX group, separate from its Solaris group, still writes perl for tooling and is only now worried who’ll pick it up when she retires. Old IT, new IT, big IT; they all write something.
Speaking as someone who’s been in IT from kernel 1.2.x, if you’re not coding then you must be running the bucket truck. Do I win?
Yeah, you’re much better off if you can at least automate stuff by writing scripts.
But, you often get people who think IT work is software and application development. And the reverse: It is often assumed programmers are good at building or troubleshooting computers and networks.
most IT work doesn’t require the ability to write any code
If you keep it small-scale, I guess. But, sooner or later unless you work in one of those finger-paint kits like checkpoint, you’re going to need to write some terraform, chef or - fuck no - Ansible. The latter is less code than codes, or perhaps a suicide note, but it’s still out there.
Hell; my boss, leading a team in an org so big and old that it’s got a dedicated AIX group, separate from its Solaris group, still writes perl for tooling and is only now worried who’ll pick it up when she retires. Old IT, new IT, big IT; they all write something.
Speaking as someone who’s been in IT from kernel 1.2.x, if you’re not coding then you must be running the bucket truck. Do I win?
Yeah, you’re much better off if you can at least automate stuff by writing scripts.
But, you often get people who think IT work is software and application development. And the reverse: It is often assumed programmers are good at building or troubleshooting computers and networks.