Complexity. There is a wealth of knowledge, best practices, and tooling in the DevOps space, and it’s intimidating to leap into yet another world when the application programming one already keeps us plenty busy.
Risk. Mistakes in DevOps have potentially devastating consequences: the software going down for users, data loss, security or privacy breaches, etc. Problems can of course happen in the application programming side but are generally less severe.
I totally get the risk factor. While application programming can be risky, it's usually much easier to rollback or fix. I might be old-school but I believe that at least senior devs should be familiar with the DevOps concept. After all, it's a pretty new domain that was rose by developers.
Yep, totally agree. And with the advent of “infrastructure as code” (like Terraform and similar) and containerization, hopefully the ease of rollback and risk factor/etc. will reduce over time, making it seem less “risky.”
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I’d add these reasons to your list:
I totally get the risk factor. While application programming can be risky, it's usually much easier to rollback or fix. I might be old-school but I believe that at least senior devs should be familiar with the DevOps concept. After all, it's a pretty new domain that was rose by developers.
Yep, totally agree. And with the advent of “infrastructure as code” (like Terraform and similar) and containerization, hopefully the ease of rollback and risk factor/etc. will reduce over time, making it seem less “risky.”