Positives The book is widely praised as a comprehensive and practical guide for understanding, explaining, and implementing DevOps culture, processes, and tools. Many consider it a must-read for anyone wanting to achieve high-performance development and operations. It effectively builds upon the foundational ideas presented in "The Phoenix Project," offering a more detailed framework for applying solutions within an organization, including aspects of information security and compliance. Reviewers appreciate its broad scope, covering organizational, cultural, and technical practices relevant to various stakeholders from upper management to development and operations. The inclusion of numerous inspiring case studies from prominent companies is consistently highlighted as a strength, providing grounded examples of how DevOps practices can improve business outcomes and offering practical advice for implementation. Readers also value its focus on the underlying philosophy and principles of DevOps rather than specific tools, making it technology-agnostic and emphasizing a crucial mindset shift.
Negatives Despite its strengths, many experienced practitioners found the book to be less useful or inspiring, often deeming it redundant due to the widespread adoption of DevOps concepts since its publication. Critics point out that much of the content is broad, high-level, and lacks the detailed technical guidance expected from a handbook, often feeling more like evangelism aimed at managers. A common complaint is its repetitive and verbose writing style, with some reviewers finding it dry, boring, or containing too much filler, suggesting it could have been significantly shorter. The book's focus on web services, Silicon Valley startups, and large enterprises is also noted as a limitation, making its applicability less universal for smaller companies, legacy systems, or hardware-controlling software. Furthermore, some readers felt that the book primarily reiterated common sense or widely known information, particularly for those already familiar with the field or who regularly follow industry blogs, and did not adequately address potential caveats or drawbacks of the practices discussed.
Conclusion Ultimately, this book serves as an excellent introduction and reference for those new to the DevOps movement, including students, technical managers seeking a high-level overview, or professionals aiming to understand the cultural and organizational aspects of modern IT delivery. It excels at demystifying DevOps by focusing on core principles like flow, feedback, and continuous learning, and how these translate into organizational change rather than just technical implementation. While seasoned DevOps practitioners might find much of the content familiar or lacking in advanced technical depth, its value as a foundational text for sparking discussions and guiding initial adoption within an organization is undeniable. It is particularly recommended for anyone looking to grasp the "soft-side" of DevOps and its impact on team structures and business outcomes, making it a valuable resource for fostering a new mindset across an entire IT department.
