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

The British government wants to build backdoors into standard encryption libraries. This means the technology that protects your financial transactions could have a backdoor. These same backdoors were just exploited in the WannaCry outbreak that just took down the NHS. Who created that backdoor? The NSA, whose incompetence allowed this "tool" to fall into the hands of a Russian government-affiliated hacking group.

You don't do anything illegal? Great! You do have a bank account, right? You do have private conversations with your significant other, right? Would you want either to be open for potentially anyone to see? Probably not. Resist government's demands to force Internet companies to open backdoors for them. Nothing good will come of it.

Backdoors are bad. There is no way to guarantee access to one group of people to a backdoor. People are fallible. Strong math

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.

Subscribe to DevOps'ish Weekly

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