Effective DevOps

Chapter 19. Conclusion

You made it all the way to the end of this book—congratulations, and thank you for reading! We covered a great deal in this book, sharing a variety of stories from a range of individuals and organizations. It is possible that you will not have the time to change every single thing you might want to, or that not every aspect of what we describe as an effective devops culture will be relevant to your current situation. Remember that there is no one-size-fits-all solution. It is important for you, either individually or with others, to identify your most pressing concerns that need to be prioritized now, the changes that can be delayed until some later date, and those that don’t currently matter to you at all.

We’ve shown you that there is no prescription for the One True Way of doing devops, devops in a box, or devops-as-a-service. We’ve shared ideas and approaches for improving individual collaboration, team and organizational affinity, and tool usage throughout an organization, and how these concepts allow organizations to change, adapt, and pivot as necessary. You have learned how these common themes can be applied in different ways to every organization that wants to improve both the quality of their products and the efficiency and well-being of their employees.

These principles apply regardless of what language you’re programming in, what tools you use to manage your infrastructure, or whether or not you’re using the latest, shiniest container ...