This talk was derived from an opensource.com article I wrote in April 2017, Golang to the rescue: Saving DevOps from TLS turmoil. Presented at GopherCon 2017 as a Lightning Talk. Source for the talk is available on GitHub. Introduction Chris Short Manager of DevOps at Bankrate opensource.com and DZone Contributor Contributed to The Open Organization Guide to IT Culture Change DevOpsDays Speaker and Organizer DevOps'ish chrisshort.net @ChrisShort Notes: Hi! I'm Chris! I manage…
The open organization community at Opensource.com (of which I'm a member) is pleased to announce the immediate release of its newest book, The Open Organization Guide to IT Culture Change.
As IT teams around the world rise to these new challenges, they're realizing that radical change isn't a matter of tools alone. It's also a matter of culture—the values that underpin behaviors, influence problem-solving capability, and facilitate truly revolutionary potential. Those values are open values.
And forward-thinking IT organizations are leveraging those principles. They're becoming more transparent, more collaborative, more mission-driven, and more agile to transform the way they work.
Consisting of more than 25 chapters from writers, practitioners, industry leaders, and notable technologists, the book explains how open principles are reshaping IT organizations today. It also offers practical advice for leaders seeking to catalyze powerful and lasting
On Tuesday, May 23, 2017, I did a DevOps talk at Open Source South Carolina. The talk was a DevOps 101-styled deep dive into DevOps. Since the number one question I get when talking about DevOps, in general, is "where do I start?" I added my "The Three Things" to the already well known "Three Ways". This provided both the holistic view while guiding people needed an extra nudge down the DevOps path.
It was a lengthy talk given the two-hour time slot. I built an enormous outline to guide myself during the talk. I am considering making the talk into an ebook when time becomes more abundant if demand is there.
The other day my Vice President asked me a question, "What would it take to turn a good SysAdmin into a DevOps engineer?" He followed it up with, "Don't spend more than ten minutes thinking about it." He was not disappointed when I told him the next day I am spending way more than ten minutes on answering the question. This is a hard question for me to answer. This is a question that you won't know if your answer is right for at least six months.
I had more than ten minutes worth of thoughts pop into my head within seconds of the question. A deluge of DevOps lessons learned washed over me. I realized that I needed to build a framework to help others embrace DevOps culture and thinking. It's not feasible to have
Disclaimer: These are real world experiences I have had within organizations that I have been employed by. Identifying information is intentionally anonymous. If you read this and think you are one of the teammates please keep that to yourself for the sake of others.
A lot of people think that DevOps, Cloud Native, Agile, GROWS, etc. are all rainbows and roses. You start small and work your way up to full blown operations or you decide as an organizational unit to change. These are the two patterns associated with a Jedi-type maturation process of DevOps. What if I told you that, like in Star Wars, DevOps has a dark side? I have seen the light side everyone thinks of and have carried the red lightsaber as well. Let's walk into the cave on Dagobah together.