3 ms·
> Devops doesn't mean "dev and ops cooperating". Fundamentally it means that devs do the ops. The problem with “DevOps” is that everyone has their own definiti
by dijit 6y ago
> Devops doesn't mean "dev and ops cooperating". Fundamentally it means that devs do the ops.
The problem with “DevOps” is that everyone has their own definition.
For some people it’s a rebranding of sysadmins that use Infrastructure-as-Code tools.
For others it’s a term meaning the breaking of Silos between development and ops.
For others it means a (primarily) developer person who can also configure Apache.
Luckily, we don’t have to guess what was meant by the term as it was clearly defined at the time of inception[0], and unfortunately the original creator of the term does not agree with you.
[0]: https://youtu.be/o7-IuYS0iSE https://youtu.be/o7-IuYS0iSE
- jedberg 6y agoI don't know why you think he doesn't agree with me. I happen to know most of the people in that video personally and have spoken to them for many hours on the topic of DevOps. I think I even saw one of my presentations in the video. I can tell you confidently that they agree with me.
- dijit 6y agoSeems odd then. Most of the material coming out at the time was telling the industry to break the silo between dev and ops. I suppose if you’re right then I fundamentally disagree. Dev and Ops chase different goals and it’s very hard for a single person to have a role that makes them responsible for everything.
- jedberg 6y ago> Most of the material coming out at the time was telling the industry to break the silo between dev and ops. Exactly. Break the silo. Make the devs do their own ops. Have ops specialists write tools to make it easer for devs to do their own ops. The fundamental point is that devs don't just "throw their code over the wall".