DevOps Foreword - Patrick Debois
Patrick on Twitter: @patrickdebois - Patrick’s blog: jedi.be
Within the DevOps commununity there is a well-known acronym (first mentioned by John Willis) called CAMS: ‘Culture, Automation, Measurement and Sharing’. Many things have been written about the first 3 parts, and yes they are important. Sharing is often taken for granted, but it isn’t:
- It takes effort to formulate the things you do, and put them in perspective.
- It takes courage to explain both the good, the bad, and the ugly in public.
Sharing has been a major part of the success of DevOps: people tweeting links, writing blogposts, organizing conferences, writing books - all under the #devops hashtag. This has allowed the community to learn from each other, to expand ideas, to finetune existing ideas.
In the old days, apprentices travelled from place to place to bring back new ideas to their guilds. They knew it was important to liberate themselves from their situation to get new perspectives, or even being able to see the problems in the right perspective. In the same vein, the book Build Quality In brings together stories from people who have been on a DevOps journey. The stories are not prescriptive so don’t expect a ‘DevOps steps 1, 2, 3’ formula. They represent the learnings of the authors within their situation. Some things might be translated directly to your work situations, others will require you to rethink your strategy.
The most important takeaway is that you are not alone on this journey and that you should actively reach out to others to learn from, and that’s what this book is all about.
I look forward to reading your blogposts, tweets, or even your own book. But first of all, start reading Build Quality In and get inspired!