4 ms·
> Regarding DevOps, a major aim was to embed operational concerns into all stages of development. In that sense, it was a massive success... I strongly disagre
by manuelabeledo 4y ago
> Regarding DevOps, a major aim was to embed operational concerns into all stages of development. In that sense, it was a massive success...
I strongly disagree here.
If it was such a success, then why are there devops jobs at all? If it was meant to signify that developers should share responsibility on deployments and integrations, what's the role of a "devops engineer"?
It seems to me that self-proclaimed devops practitioners tend to draw lines to limit their responsibility in the software building process, which is also counterproductive.
- falcor84 4y ago>devops practitioners tend to draw lines to limit their responsibility in the software building process I'd say you hit the nail on the head here. I would agree that DevOps does indeed stem from operations folks saying that they don't want full responsibility for how software runs in production, instead introducing tooling and processes to force more of these concerns onto devs. As to terminology, "DevOps engineers" are ops engineers who adhere to this approach (or being a bit cynical, those who just have familiarity with relevant tooling and like the sound of that term). And as to whether this is productive or not, I would argue that it's made the individual developer somewhat less productive on the metric of "writing code", but the overall organization more productive on the metric of "deploying working code that serves users".
- hgsgm 4y ago
- throwaway5959 4y agoDevOps is like what happened to DBAs, now devs get to do another role while still being responsible for their other roles without extra compensation while eliminating a whole job (ops or dba).