Free Book Online
Book Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale

Pdf

Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale

2.2 (3066)

Log in to rate this item

    Available in PDF - DJVU Format | Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale.pdf | Language: ENGLISH
    Ryn Daniels(Author)

    Book details


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 Ryn 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

Building a Culture of Collaboration, Affinity, and Tooling at Scale Jennifer Davis is a global organizer for devopsdays and a local organizer for devopsdays Silicon Valley, and the founder of Coffeeops. She supports a number of community meetups in the San Francisco area. In her role at Chef, Jennifer develops Chef cookbooks to simplify building and managing infrastructure. She has spoken at a number of industry conferences about devops, tech culture, monitoring, and automation. When she's not working, she enjoys hiking Bay Area trails, learning to make things, and spending quality time with her partner, Brian, and her dog, George.Ryn Daniels is an infrastructure operations engineer working at TravisCI. They have taken their love of automation and operations and turned it into a specialization in monitoring, configuration management, and operational tooling development. Ryn has spoken at numerous industry conferences, including Velocity, devopsdays and Monitorama, about subjects such as infrastructure automation, scaling monitoring solutions, and cultural change in engineering. Ryn wants to help organizations bring modern development practices and human-first culture design to their ops teams to make engineering practice more effective, efficient, and fun. They live in Brooklyn with a perfectly reasonable number of cats and in their spare time can often be found powerlifting, playing cello, or handcrafting knitted server koozies for the data center.

3.4 (11310)
  • Pdf

*An electronic version of a printed book that can be read on a computer or handheld device designed specifically for this purpose.

Formats for this Ebook

PDF
Required Software Any PDF Reader, Apple Preview
Supported Devices Windows PC/PocketPC, Mac OS, Linux OS, Apple iPhone/iPod Touch.
# of Devices Unlimited
Flowing Text / Pages Pages
Printable? Yes

Book details

  • PDF | 410 pages
  • Ryn Daniels(Author)
  • O'Reilly Media; 1 edition (June 24, 2016)
  • English
  • 2
  • Computers & Technology

Read online or download a free book: Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale

 

Review Text

  • By Dan on July 1, 2016

    The subtitle says it all. This book has an extremely strong emphasis on the cultural aspects for creating an atmosphere suitable for the development of a solid devops practice. It has a liberal focus on the presumed importance of team (and workforce) diversity (ethnic background, race, gender, sexuality, age, etc.) and its centrality to creating a devops culture. This belief sets the mood of the entire book, from the topics, to the tone, to the writing style. Its difficult to find a page where this theme isn't drilled home in one way or another - sometimes plainly, sometimes more subtlety. For example, there is a sidebar section describing the personal challenges of a deaf (female) developer. While the story was surely interesting, I couldn't help but feel that it was out of place. This kind of thing is everywhere in this book, to the point of being distracting.If you are expecting advice or direction on hardcore tooling or technology, this is definitely not the book for you. It is much more in line with HR and management-themed books on building diverse teams, handling conflicts, building collaboration, and then applying everything at scale. The authors even point out that people might be surprised by the apparent lopsided emphasis, especially when compared to just about every book in this space. You could change the word "Devops" in the title to just about any corporate practice you wanted to and much of the book could stay as is.The authors make a strong and compelling case for devops as a cultural change - for them it is far less about the tools, processes, and technologies associated - it's about the people. This rings true with my own experiences in this space. However, I do not believe they made the case for such a strong emphasis on diversity as a requirement for success in that change. This premise so strongly permeates the book that one wonders if they were trying to convince themselves of its centrality. It's as if they believe a typical IT organization (which they point out is staffed mostly by white, cisgender males) couldn't possible be successful at making the cultural transformation.Still, the down-to-earth tips they present are tried-and-true. I found the chapter on collaboration particularly useful. All-in-all it's a practical, worthy addition to your bookshelf.

  • By David A. Wasmer on July 21, 2016

    This book is not about DevOps. It is not a technical book, a lean workflow book, a managerial book, or even a business book. It is a sociopolitical book that would be more at home in a Women's Studies course. It has a political agenda: promote cultural, racial and sexual diversity. There is nothing wrong with the topic, but there is something wrong with both the title and the publisher of this book. Typically, the publisher provides the book's title and the title of this book is deceptive. O'Reilly is known for publishing quality books about computer technology. This book is not about computers or technology. My opinion of O'Reilly is worse after reading this book. I will be more careful when buying their books in the future to ensure the title actually relates to the contents of the book.Edit: After Goolag fired James Damore, I decided to revisit this review. The Diversity Brown Shirts are creating a hostile work environment. It has become so hostile that they will fire people who do not hold politically correct views. The only way to stop these Brown Shirt tactics is by exposing them for what they are. If you want to balance your knowledge on the politics of hiring, promoting, team building, collaboration, and other general HR topics, I recommend two things. First, read James Damore's ten-page memo and watch some of his interviews on YouTube. Second, read the following book. (Note: at least the title of this book is honest about its topic.)Death by HR: How Affirmative Action Cripples Organizations Paperbackby Jeb Kinnison

  • By Jediator on July 18, 2016

    I brought this book because my current assignment on a DevOps project. I was very disappointed after going through the whole book. First, the book title is really misleading. It should be called "Effective Human Resource Management" or "Organizational Dynamics", because of lack of technical substances. Second, the authors declared at the beginning that they wanted to illustrate the DevOps concepts through story telling, but there weren't many stories in the book, except a short one in the beginning about Etsy's DevOps process. The other real world story in the book was about USPTO's DevOps, but without any performance results on how DevOps actually improved USPTO's business process. Considering how long a patent application takes today and how slow and difficult to use the USPTO's patent search application is (compared to Google patent), the USPTO's DevOps story probably isn't very convincing. Third, most content in the book are just common sense ideas that people would already know if they had worked in a development or operation shop for a while. The book lacks concrete examples to support authors' ideas, and fails to present a consistent and coherent view of how DevOps works in different enterprise environment. Since the authors claimed to have researched and interviewed many companies doing DevOps, it would be more convincing to tell some of the company stories, either successful or unsuccessful, to demonstrate what DevOps really is and how it works to help organizations improve their business bottomline, and what to do to reduce implementation risks of DevOps.


  • Name:
    Email*:
    The message text*: