You probably think I’m going to talk about all the reasons why you should use open source tooling as the foundation for an effective DevOps culture in your organization, but that’s not what this is about. Not to marginalize the complexity of the challenges faced by the team I work with, but I have confidence that the engineers are going to figure the tooling part out. Believe it or not, the daunting part is wrapped in cultural change.
I have spent a significant amount of time reading about cultural change, what you need to have an effective DevOps community, how you build high functioning teams, and asking the question, “How do I DevOp?” The ideas I’ve read have given me a few new things to stick in my tool belt. However, nothing has resonated with me as much as this:
