There are not very many ops people who cannot code. Especially these days. I spent at least the last 20 years doing ops. Ops people are HIGHLY motivated to create things that DON’T FAIL. However, ops teams are often blocked by MANAGERS from doing essentially development in the prod environment. I’m talking about tools and scripts. At the places I’ve worked with the highest uptime, it was because ops had an unlimited, unfettered free hand.

Remove the handcuffs from your ops team and your reliability will SOAR.

▲

verdverm 7 hours ago | parent | next [-]

Average ops have never been less capable and adverse to programming than now. The problem is getting worse, not better. I know because I am in ops and one of the few who loves to code and accidentally entered the field

▲

bigstrat2003 17 minutes ago | parent | next [-]

No way. I have worked in ops for 20 years now; almost everyone knows how to code. Some enjoy it and some don't, but people are capable of it and will do it when needed.

▲

rcoder 3 hours ago | parent | prev | next [-]

I think that any kind of “modern ops” necessarily includes coding, even if there isn’t a ton of Python or Rust being generated as part of the workflow.

Kubernetes deployment configurations and Ansible playbooks are code. PromQL is code. Dockerfiles and cloud-init scripts are code. Terraform HCL is code.

It’s all code I personally hate writing, but that doesn’t make it less valid “software development” than (say) writing React code.

	▲	CaveTech 3 hours ago \| parent [-]
		These things are not nearly equivalent. It’s writing code, it’s not software engineering.

▲

0xbadcafebee 3 hours ago | parent | prev [-]

But the same is true of devs. Many of them are pretty clueless about coding. It's a whole generation of "bootcamp people" who were designers or bartenders and heard there were more lucrative jobs.

▲

cindyllm 5 hours ago | parent | prev [-]

[dead]