Scan barcode
benyoda95's review against another edition
5.0
Fantastic. This book was hugely informative about the prices we can be driving for. I found the QA section especially helpful.
originalhat's review against another edition
5.0
A far reaching book that is part technical and part philosophical. The DevOps Handbook gives broad and directed insight into the effects of a highly functional paradigm that ecourages openess, trust and experimentation. The importance of quality telemetry should and cannot be understated.
Make small, incremental and inclusive decisions based on data, not assumptions–show others the potential of creating effective feedback loops and informatics that can be amplifed. At the end of the day, we must prioritize the improvement of daily work over daily work itself.
Make small, incremental and inclusive decisions based on data, not assumptions–show others the potential of creating effective feedback loops and informatics that can be amplifed. At the end of the day, we must prioritize the improvement of daily work over daily work itself.
adamchalmers's review against another edition
4.0
This book does a really good job at explaining strategies to get your software work done faster and more reliably. I really enjoyed the case studies from real companies. I've sl0wly been putting these ideas into practice on my team, and it's making my production deploys way less anxiety-inducing.
grubnubble's review
3.0
Because the project of writing this book began about ten years ago, many parts of the book are already quite dated. Worth a read for some interesting details, gobs of “case studies,” and holistic, humane perspectives on work.
chrisxaustin's review against another edition
5.0
i had high hopes for this book since the authors have been very influential for me, especially gene kim - i've listened to every episode of the idealcast and follow anything he works on.
On page 8 i felt a keen sense of disappointment when the book stated that it would be focusing on lead time to deploy (or similar), as that's only one facet of DevOps. I was worried that it was going to just be about CICD, which seemed out of character, given how much Gene focuses on organizational health, structure and dynamics, leadership, etc.
That fear passed very quickly in the following pages when I saw what they were doing - it isn't only focusing on shipping faster, it's about *all* the things you need to do before you can deliver value quickly, safely, and sustainably.
This includes value stream thinking, cross functional teams, testers embedded with teams and acting as enablers, shifting compliance and security left, reducing batch size, building psychological safety, measuring team health (eNPS, SPACE, etc), identifying types of waste (Making Work Visible is also good for this), types of work (flow framework), OKRs, coaching katas, fast bidirectional feedback, reducing planning overhead and coordination overhead, feature flags, dark launches, A/B testing, Gemba walks, non-functional requirements (the ilities), elevating the improvement of daily work over the work itself, and a discussion of trunk-based work vs feature branches (I prefer short-lived feature branches that are continually updated from main)
I've read all of these subjects before, but having them all as part of a single narrative was valuable for collecting my thoughts.
On page 8 i felt a keen sense of disappointment when the book stated that it would be focusing on lead time to deploy (or similar), as that's only one facet of DevOps. I was worried that it was going to just be about CICD, which seemed out of character, given how much Gene focuses on organizational health, structure and dynamics, leadership, etc.
That fear passed very quickly in the following pages when I saw what they were doing - it isn't only focusing on shipping faster, it's about *all* the things you need to do before you can deliver value quickly, safely, and sustainably.
This includes value stream thinking, cross functional teams, testers embedded with teams and acting as enablers, shifting compliance and security left, reducing batch size, building psychological safety, measuring team health (eNPS, SPACE, etc), identifying types of waste (Making Work Visible is also good for this), types of work (flow framework), OKRs, coaching katas, fast bidirectional feedback, reducing planning overhead and coordination overhead, feature flags, dark launches, A/B testing, Gemba walks, non-functional requirements (the ilities), elevating the improvement of daily work over the work itself, and a discussion of trunk-based work vs feature branches (I prefer short-lived feature branches that are continually updated from main)
I've read all of these subjects before, but having them all as part of a single narrative was valuable for collecting my thoughts.
jakehayes's review against another edition
4.0
It's a good book for starting out in dev-ops or agile methodologies. It's very focused on why and how to do it, so if you have experience setting it up or working with it already, someone else probably read this already and provided that information to you.