Showing posts with label DevOps. Show all posts
Showing posts with label DevOps. Show all posts

Wednesday, December 3, 2014

DevOps in 2015

Chris Jackson, CTO of DevOps Services at Rackspace, recently published the article "Will 2015 be the DevOps tipping point?" on venturebeat.com. A few comments about it follow:

  • Having been in DevOps now for years its hard to see 2015 as a pivotal year in my own career, however I can understand why it may be for DevOps in the industry. I was lucky enough to work for a CTO at Zynx Health in 2012, Mark Long, that believed in the benefits of DevOps back in 2012 when I transitioned into the role of DevOps engineer at Zynx Health. Mark Long is still in the minority according to the article, which states only 7% of CTO drive DevOps.
  • My experience makes it understandable that the article indicates that it is "the operations team that is tasked with implementing and managing the [DevOps] program". My experience reflects this reality in my current role of Lead Systems Engineer at Zynx Health. My team is primarily operation's personnel with DevOps practices and technology as part of our core competencies.

Saturday, December 22, 2012

Prallel: DevOps Practices and Matthew 7:3

In a recent article by Michael Stanhke, he specifies that one of the practices of a DevOps culture includes "Admit Failure, Build Trust". This got me thinking about how similar DevOps intends to be the embodiment of teachings in the bible about human interaction. His article can be found here: ""Day 12 - Devops is a Mindset; a Cultural Case Study" on SysAdvent.

DevOps is a movement for improving the cultural interactions of technologists. Especially those of different distinct roles, for example developers and operations persons.

Matthew 7:3 - This is part of the bible, an individual sentence in the teaching of Jesus, in the well known section "Sermon on the mount".  The American Standard Version provides the following translation: "And why beholdest thou the mote that is in thy brother's eye, but considerest not the beam that is in thine own eye?"

In Michael's blog post the "Admit Failure, Build Trust" section says the following:
Post-mortem meetings were a major exercise in blame-storming. I decided that instead of redirecting blame or telling customer groups to design for failure, I would just own the failure. I walked in and said, “hey, we totally screwed up,” continuing with a prepared statement in how we misconfigured some enterprise storage and totally blew up many lines of business when it went wrong. 
The response was amazing. People were left with “oh...um ok then.” No blame and no problems. Honesty panned out! That success drove me to run every post-mortem like that: If was our fault, we shouted it. 
Transparency builds trust.

These type of writings help to bridge the gap between the theological and practical in the work place. Along with bringing truth documented about 2000 years ago into the presence.  Both are difficult to accomplish.  Being part of the DevOps movement as a DevOps Engineer myself and being a believer in Jesus, I appreciate the parallels, maybe you do too. Comments welcome on this post.