<p>I've never seen ops dev used before this post.  Searching around I see things like <a href="https://dzone.com/articles/opsdev-or-devops" rel="nofollow noreferrer">this article that has it in the title but nowhere in the article</a>.  Then there's <a href="https://devops.com/devops-must-also-mean-opsdev/" rel="nofollow noreferrer">this article</a> from 2015:</p>

<blockquote>
  <p>So in this way, when “OpsDev” happens, IT ops teams are helping developers do their jobs, but developers are also architecting applications with IT ops in mind, helping them utilize resources better. The days of developers simply creating applications and “throwing them over the fence” to testers and IT ops teams are over.</p>
</blockquote>

<p>which seems to define OpsDev as "development in a company that practices DevOps" (or more cynically, "development done correctly").</p>

<p>Finally, there's <a href="https://dzone.com/articles/opsdev-is-coming" rel="nofollow noreferrer">https://dzone.com/articles/opsdev-is-coming</a> :</p>

<blockquote>
  <p>What Is OpsDev?
  OpsDev means that the dependencies of the various application components must be understood and modeled first before the development process begins. In addition, the consideration for infrastructure stability, environment modeling, security and audit/compliance measures are first and foremost. Application components are stubs and they do not need to be in their final forms. Secondly, the environments in which the components will be deployed for production must be modeled. Thirdly, the processes to deploy the various components to the target environments must be automated as much as possible.</p>
</blockquote>

<p>Again, this sounds to me just like normal, modern development.</p>

<p>DevOps is a problematic term because <a href="https://devops.stackexchange.com/q/788/960">it has many different definitions</a>.  OpsDev, on the other hand, appears to have essentially <em>no</em> definitions.  From a personal perspective, I would mentally substitute "development" for every instance of "OpsDev" and ignore the term; it appears to be just another instance of people inventing new terminology to describe old concepts so that they sound more exciting.</p>

CC BY-SA 4.0
2018-11-24T03:37:02.117Z
We had this once smb used spontaneously and less formally to underline IaaS programming but also Dockerization provided by the Ops team.
Ta Mu
CC BY-SA 4.0
2018-11-21T21:37:35.750Z
2018-11-21T21:37:35.750Z
Xiong Chiamiov
<p><em>In the operations team <strong>DevOps</strong> does not trust developers to make changes to the production infrastructure</em>. Developers want to focus on their application and the value it delivers to the organization. Developers want to know the characteristics of the infrastructure but do not want to build it or operate it.</p>

<p>The operations team is absolutely critical to the success of DevOps methodologies. </p>

<p>The developers must be able to trust that the infrastructure has specific characteristics: characteristics like performance, connectivity, availability, and uniformity. </p>

<p>To enable this trust, I believe that the operations teams are going to need to become more like developers. I call this <strong>OpsDev</strong>.</p>

<p><strong>OpsDev is not simply about having a scripted build for servers. OpsDev is about having a full infrastructure that is built and maintained automatically from a set of source-controlled configuration files, and then having development and test environments that are built using the same methodology.</strong></p>

<p>Source: <a href="https://www.astroarch.com/tvp_strategy/devops-requires-opsdev-time-change-35139/" rel="nofollow noreferrer">https://www.astroarch.com/tvp_strategy/devops-requires-opsdev-time-change-35139/</a></p>

CC BY-SA 4.0
2024-09-07T02:11:03.750Z
I fully agree, it is what I did in a 50 Million Dollar Project. I coached the Operational Engineers, Linux Geeks and great smokers alike in software engineering. then they started writing good code, infrastructure code. they became SWEs. BUT........ with the vast knowledge of Information Technology, Networking and Linux Kernel expertises. Not the narrow knowledge of most of the highly siloed developers I met during the past 30 years. *ymmv
Stephan K.
CC BY-SA 4.0
2018-11-21T21:25:15.903Z
2018-11-21T21:25:15.903Z
BlueSeph
<p>I've heard both terms, but I can't differentiate between the two.</p>

<terminology>
What's the difference between "Ops Dev" and "DevOps"?
user10994
# What's the difference between "Ops Dev" and "DevOps"?

(Asked by: username_0 on 2018-11-21)

I've heard both terms, but I can't differentiate between the two.

**Tags:** terminology


---

## 2 answers

### Answer by username_1 on 2018-11-21. Score: 2

I've never seen ops dev used before this post. Searching around I see things like [this article that has it in the title but nowhere in the article](https://dzone.com/articles/opsdev-or-devops). Then there's [this article](https://devops.com/devops-must-also-mean-opsdev/) from 2015:

> So in this way, when “OpsDev” happens, IT ops teams are helping developers do their jobs, but developers are also architecting applications with IT ops in mind, helping them utilize resources better. The days of developers simply creating applications and “throwing them over the fence” to testers and IT ops teams are over.

which seems to define OpsDev as "development in a company that practices DevOps" (or more cynically, "development done correctly").

Finally, there's <https://dzone.com/articles/opsdev-is-coming> :

> What Is OpsDev?
> OpsDev means that the dependencies of the various application components must be understood and modeled first before the development process begins. In addition, the consideration for infrastructure stability, environment modeling, security and audit/compliance measures are first and foremost. Application components are stubs and they do not need to be in their final forms. Secondly, the environments in which the components will be deployed for production must be modeled. Thirdly, the processes to deploy the various components to the target environments must be automated as much as possible.

Again, this sounds to me just like normal, modern development.

DevOps is a problematic term because [it has many different definitions](https://devops.stackexchange.com/q/788/960). OpsDev, on the other hand, appears to have essentially *no* definitions. From a personal perspective, I would mentally substitute "development" for every instance of "OpsDev" and ignore the term; it appears to be just another instance of people inventing new terminology to describe old concepts so that they sound more exciting.

> **Comments:**
> **username_2**: We had this once smb used spontaneously and less formally to underline IaaS programming but also Dockerization provided by the Ops team.  

---

### Answer by username_3 on 2018-11-21. Score: 0

*In the operations team **DevOps** does not trust developers to make changes to the production infrastructure*. Developers want to focus on their application and the value it delivers to the organization. Developers want to know the characteristics of the infrastructure but do not want to build it or operate it.

The operations team is absolutely critical to the success of DevOps methodologies.

The developers must be able to trust that the infrastructure has specific characteristics: characteristics like performance, connectivity, availability, and uniformity.

To enable this trust, I believe that the operations teams are going to need to become more like developers. I call this **OpsDev**.

**OpsDev is not simply about having a scripted build for servers. OpsDev is about having a full infrastructure that is built and maintained automatically from a set of source-controlled configuration files, and then having development and test environments that are built using the same methodology.**

Source: <https://www.astroarch.com/tvp_strategy/devops-requires-opsdev-time-change-35139/>

> **Comments:**
> **username_4**: I fully agree, it is what I did in a 50 Million Dollar Project. I coached the Operational Engineers, Linux Geeks and great smokers alike in software engineering. then they started writing good code, infrastructure code. they became SWEs. BUT........ with the vast knowledge of Information Technology, Networking and Linux Kernel expertises. Not the narrow knowledge of most of the highly siloed developers I met during the past 30 years. *ymmv  

---

