Admins who do Dev work should be called OpsDev ...
A DevOps, is a Developer , someone who started as a developer and now do extra admin and systems work
Not the other way around ..
On the flip side I seen just how poorly Dev managers and Dev team leads can understand Ops. It is even worse when they think they do, but don't. This can make Devops painful.
There is also a problem with having an individual Devops on each Dev team. You will end up with each Dev team doing things completely different ways. One will be Ubuntu, one Debian, one CentOS, one instances, and one containers. There should be some standardizing force across the teams.
a Developer that does extra stuff
there is a huge difference between a developer who does extra stuff, and a system engineer who does .. extra stuff
the barrier of entry to becoming a developer is a lot bigger than the barrier of entry to become an admin or system engineer
Eh. Spinning up a new VM is wayyyyy easier than racking a new box. And deploying to an app-running service is generally way easier than managing a bare-metal/load-balancer/etc-interfacing deploy script.
A devops engineer building and maintaining that infrastructure is a split that makes sense to me, but generally doesn't obviate the need for systems/network admins and engineers, as you still have problems and issues with the underlying things often come up (sometimes it's outsourced to a cloud provider, though).
the article of this thread/post have a very nice diagram at the top .. if the DevOps is focused more on the tasks on the right (ops) in my opinion he is not really a Devop
Builder are maintainers of the infrastructure are not DevOps .. they are just Admins
Developers of the software used to make this infrastructure possibles, are just Developers