Jennifer Davis and Katherine Daniels - Effective DevOps

by Jennifer Davis and Ryn Daniels

Copyright 2016 Jennifer Davis and Ryn Daniels. All rights reserved.

Printed in the United States of America.

Published by OReilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472.

OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com .

• Editor: Brian Anderson
• Production Editor: Colleen Lobner
• Copyeditor: Rachel Monaghan
• Proofreader: Jasmine Kwityn
• Indexer: WordCo Indexing Services
• Interior Designer: David Futato
• Cover Designer: Randy Comer
• Illustrator: Rebecca Demarest

• June 2016: First Edition

See http://oreilly.com/catalog/errata.csp?isbn=9781491926307 for release details.

The OReilly logo is a registered trademark of OReilly Media, Inc. Effective DevOps, the cover image of a wild yak, and related trade dress are trademarks of OReilly Media, Inc.

While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.

978-1-491-92630-7

[LSI]

There is a sea change happening in software development and operations, and it is not simply the introduction of a new word into our lexiconits much more than that. It is a fundamental shift of perspective in the design, construction, and operation of software in a world where almost every successful organization recognizes that software is not something you simply build and launchit is something you operate.

What makes this shift unique is that its more encompassing, more holistic, and more reflective of the reality that engineering teams face on a daily basis. Long gone are the days that manufacturing and assembly-line metaphors could be used in software development and operations. Long gone are the days that products are things that are designed, planned, and then finally launched. There is no finally anymore. There is only an endless cycle of adaptation, change, and learning.

What Ryn and Jennifer have laid out in this volume is a myriad of threads to pull on as engineers in teams and organizations cope with the complexity that comes with trying to make their work simple.

Ryn and Jennifer do not paint a picture of one-size-fits-all or deterministic solutionism. Instead, they describe a landscape of topic areas, practices, and observations of teams and organizations that understand the idea that at the heart of good products, good user experiences, and good software is the elegantly messy world of human cooperation, thoughtful critique, effective collaboration, and judgment.

In 2009, my friend Paul Hammond and I gave a presentation at OReillys Velocity Conference entitled 10+ Deploys a Day: Dev and Ops Cooperation at Flickr. While some of the material was about perspectives on continuous deployment, many chose to focus on the 10+ Deploys part rather than the Cooperation part. I believe it is a mistake to think that the technology or hard parts can be seen as somehow distinct or separate from the social and cultural soft partsthey cannot. They are inextricably linked and equally critical to success. In other words, people and process influence tools and software in more ways than most are willing to admit or even know.

My strong advice to readers: do not make the mistake of thinking that technology is not about people and process, first and foremost. Your competition will eat you alive the second you start thinking this.

These topics of concern are not found in typical computer science curriculums, nor are they found in typical professional leadership and development courses. These topics are born out of the pragmatic maturity that only hard-won work in the field can produce.