Why Twenty Years of DevOps Has Failed to Do It

Re:Why Twenty Years of DevOps Has Failed to Do It by rcoder on Saturday January 17, 2026 @10:55PM (#46664656)

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.

[ Parent | on HN ]

Re:Why Twenty Years of DevOps Has Failed to Do It by CaveTech on Saturday January 17, 2026 @11:02PM (#46664686)

These things are not nearly equivalent. It’s writing code, it’s not software engineering.

[ Parent | on HN ]

Re:Why Twenty Years of DevOps Has Failed to Do It by SlightlyLeftPad on Sunday January 18, 2026 @04:28AM (#46666244)

Correct, it’s systems engineering.

[ Parent | on HN ]

Re:Why Twenty Years of DevOps Has Failed to Do It by verdverm on Sunday January 18, 2026 @06:03PM (#46673096)

It's configuration management, systems engineering is low level imo

[ Parent | on HN ]

Re:Why Twenty Years of DevOps Has Failed to Do It by SlightlyLeftPad on Sunday January 18, 2026 @07:49PM (#46673802)

I think you have it backwards. Systems engineering is the big picture discipline of designing & managing complex systems while config management is a specific process within that.

[ Parent | on HN ]