4 ms·

DevOps, is a developer, that do admin stuff, because the development environment became more complex with the introduction of virtualization , cloud technologie

DevOps, is a developer, that do admin stuff, because the development environment became more complex with the introduction of virtualization , cloud technologies and big data 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 ..

edgan 9y ago
I kind of agree with you that having this distinction would be useful. The real key is it isn't about "dev work". It is a cross between Ops, Dev, and Build. The build is actually more important than the Dev. Even bigger is who you report to. In the old world as Ops you reported to an Ops manager. The to Devops is that you report to the Dev manager, hence breaking down the silos. You could just call it Devops, but I call it embedded Devops to be clearer. 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.
- systems 9y ago
  the key point i was trying to highlight, is that .. DevOps .. is really a Developer .. not a system engineer 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
majormajor 9y ago
> the development environment became more complex with the introduction of virtualization , cloud technologies and big data 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).
- systems 9y ago
  honestly i am not really sure what you mean by "a split that makes sense to me", split between who? 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

edgan 9y ago

I kind of agree with you that having this distinction would be useful. The real key is it isn't about "dev work". It is a cross between Ops, Dev, and Build. The build is actually more important than the Dev. Even bigger is who you report to. In the old world as Ops you reported to an Ops manager. The to Devops is that you report to the Dev manager, hence breaking down the silos. You could just call it Devops, but I call it embedded Devops to be clearer. 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.

systems 9y ago
the key point i was trying to highlight, is that .. DevOps .. is really a Developer .. not a system engineer 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

majormajor 9y ago

> the development environment became more complex with the introduction of virtualization , cloud technologies and big data 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).

systems 9y ago
honestly i am not really sure what you mean by "a split that makes sense to me", split between who? 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