Image from Amazon Title: Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale
Author(s): Jennifer Davis and Katherine Daniels
O'Reilly wrote:Some companies think that adopting devops means bringing in specialists or a host of new tools. With this practical guide, you’ll learn why devops is a professional and cultural movement that calls for change from inside your organization. Authors Katherine Daniels and Jennifer Davis provide several approaches for improving collaboration within teams, creating affinity among teams, promoting efficient tool usage in your company, and scaling up what works throughout your organization’s inflection points.
Devops stresses iterative efforts to break down information silos, monitor relationships, and repair misunderstandings that arise between and within teams in your organization. By applying the actionable strategies in this book, you can make sustainable changes in your environment regardless of your level within your organization.
Explore the foundations of devops and learn the four pillars of effective devops
Encourage collaboration to help individuals work together and build durable and long-lasting relationships
Create affinity among teams while balancing differing goals or metrics
Accelerate cultural direction by selecting tools and workflows that complement your organization
Troubleshoot common problems and misunderstandings that can arise throughout the organizational lifecycle
Learn from case studies from organizations and individuals to help inform your own devops journey
The first thing to note is that the full title of this book is "Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale ". It covers many aspects of dev ops; not just the tooling ones that us developers like to read about it. This is good because all the aspects are important. The book really lays upon you the idea that DevOps is about culture. If you don't come away from the book thinking about the non tooling aspects of DevOps, I'd be surprised.
There are 6 parts to the book. I really liked parts I, IV, V and VI. Parts II and III felt like a bit of a slog.
The first part is six short chapters giving an overview of concepts and terms. This was very fast moving and had some good quotes and concepts. It was a lot lighter to read than your typical O'Reilly book while still teaching you what you'd want to know. The "history of dev ops" going back to the first computer felt like a bit much, but it is an intro. I was surprised to see the word "portmanteau" in the book multiple times. I just learned that word last year so I think it could have used a definition. Chapter six is the four pillars of dev ops and came in at 2.5 pages. I liked this as it highlighted something simple to remember as a really important concept.
The next four parts are about the pillars. The first two pillars are collaboration and affinity. It took me most of the week to get through this material. It's management/soft skills type stuff. Unfortunately for me, this is when the typical O'Reilly style showed up. A lot was covered quickly and succinctly. And a lot wasn't new. These sections could have used more examples. I thought there'd be more examples from Etsy since they have such strong practices. Preferably sprinkled through the chapter to aid in alertness. The last chapter of each part covers anti-patterns. The style of these chapters was easier to read and they were shorter. The other two pillars are tools and scaling. Those were easier for me to read. I also felt like there were more case studies sprinkled in for scaling which was helpful. The variety of companies covered in the case studies was also helpful. I also liked the emphasis in the last part for stories and how to use them well.
I did come away with new ways of looking at concepts which is important in this type of books. I like the “new words” like islands instead of silos and thinking about folk models.
I give this book 8 out of 10 horseshoes.
Disclosure: I received a review copy of this book from the publisher for reviewing it on behalf of CodeRanch.