Development-centric folks tend to come from a mindset where change is the thing that they are paid to accomplish. The business depends on them to respond to changing needs.

Operations folks tend to come from a mindset where change is the enemy.  The business depends on them to keep the lights on and deliver the services that make the business money today.

I have been part of many development groups. As part of the development team, you always like to use whatever is the latest (anything that shines will do). But QA and Operations look at things from a different perspective. Your Ferrari will come to a screeching halt when you arrive at the QA and OPS land (no offence meant here). But, in today’s world organizations cannot afford to operate in that mode. Many organizations are adopting the idea of DevOps in order to increase the collaboration  between development and operations group.




dev vs ops


Some organizations have capability to support ten deployments per day.This daily deployment cycle would be much higher at organizations producing multi-focus or multi-function applications. How do they do it?

DevOps enables the benefits of Agile development to be felt at the organizational level. This concept revolves around the fact that “More and smaller changes–mean less risk”. This concept has introduced a new role called “Release coordinator” in the enterprise IT. The primary task of this role is to coordinate the deployments of enterprise software to pre-production environments.

Many organizations creates groups (hard line drawn between development and operations) that somehow increases this friction. Where as companies like Amazon have created groups which are completely responsible for a given service. The team is responsible for scoping out the functionality, architecting/designing, building it, and operating it. What they have done is, developers are also given operational responsibilities. According to their CTO, this has increased the overall quality of the services both from customer and technology point of view. I must agree with this mindset of You build, you run it.

At Boing ( I was told), all the design engineers are also supposed to fly during the test flights. Imagine what kind of impact this will have on the designers and who build it!. Similarly when developers are also made part of the operational experience (pagers going off in the middle of the night due to outage etc.), things will change for the better for sure.


  1. Sandeep says:

    Very well said.. my beef with developers is that they do not take any accountability for their code in production.. I would like to see Developers wear the Ops hat especially for highly dynamic applications which change on a daily basis.. the quality of code will go up all of a sudden

  2. Sandeep says:

    Also.. I don’t think that Ops minded folks think that change is an enemy.. Unregulated change, not well tested code and code that does not scale well from the dev/test environment to production is what we don’t like..As you mentioned..Enterprise architecture is a very important discipline

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: