HiveBrain v1.2.0
Get Started
← Back to all entries
gotchaMajor

Why does development oppose operations?

Submitted by: @import:stackexchange-devops··
0
Viewed 0 times
whyopposeoperationsdevelopmentdoes

Problem

I'm still a student, but I'm not knowledgeable about operations, and my English is still bad.

My question is: Why does development oppose operations? When does developing oppose operations?

Solution

The point of DevOps, is that development shouldn't oppose operations, instead they should support each other.

Traditionally, due to waterfall deployments and large scale updates, development would cause operations a variety of problems when deploying due to inadequate testing, changing server environments, the list goes on and on. Essentially, the updates were too large for the operations team to be able to effectively deploy them without some problems arising in the process. These problems might be why you believe that development opposes operations.

On the other hand, DevOps works to reduce update size, decrease rigid environments, and generally improve the handoff of the application between development and operations by increasing the amount of times the handoff occurs each year. With the increased number of deployments comes less headaches for operations, because they have either automated a large amount of work required to update the products, or they better anticipate and prepare for the updates.

Tldr: DevOps aims to nullify the theory that development opposes operations by creating a mindset where operations and development work together to frequently deploy products in a timely and easily reproducible way.

Context

StackExchange DevOps Q#302, answer score: 24

Revisions (0)

No revisions yet.