Scan barcode
gigahurt's review
4.0
Not as amazing as the first time I read Continuous Delivery, but still a good book that points us in the right direction.
bvw_tri's review
5.0
Slowly whittled this down by reading 1 chapter a day. Outstanding resource that helps me understand the processes and lingo...much to learn still
andycr15's review
3.0
It might be 3 stars is a little harsh as maybe it's just not directed at me (Delivery Lead/Scrum Master of a web team). Being quite new to this role and even this whole genre, I've read quite a few books on this new world and this one has provided me less than most others.
Either it was too detailed, low level for my needs, or too high level, above my pay grade stuff, with only a few bits giving me ideas on what I can do with my team.
Either it was too detailed, low level for my needs, or too high level, above my pay grade stuff, with only a few bits giving me ideas on what I can do with my team.
bqta's review
2.0
The good: This book describes some useful principles and practices, and it ties them together into a framework. Some of it is supported by data.
The bad: This could probably be condensed to about 1/3 its current length, without losing any valuable information. It is absolutely loaded with quotes and references that add nothing, and actually make it much harder to sift out the useful information. The viewpoint is squarely planted in the world of web development, so if that isn't your field you're going to have to figure out how to adapt the useful bits yourself. Practices are rarely described in detail, and downsides/potential pitfalls are barely mentioned.
Save yourself a bunch of time and money: Get a list of the chapter headings, and look up the ones you aren't familiar with. You won't be missing anything, I promise.
The bad: This could probably be condensed to about 1/3 its current length, without losing any valuable information. It is absolutely loaded with quotes and references that add nothing, and actually make it much harder to sift out the useful information. The viewpoint is squarely planted in the world of web development, so if that isn't your field you're going to have to figure out how to adapt the useful bits yourself. Practices are rarely described in detail, and downsides/potential pitfalls are barely mentioned.
Save yourself a bunch of time and money: Get a list of the chapter headings, and look up the ones you aren't familiar with. You won't be missing anything, I promise.
dsayling's review
5.0
What a great 'how to do it by the book' book. This book focuses on adaptive challenges and technical ones. Which are imperative in a DevOps transformation. I'm trying to get all of engineering in my organization to read this
basepi's review
4.0
This book is the best resource on DevOps that I’ve found.
DevOps is a fraught topic. It’s come to mean so many things to so many people. And I’m increasingly convinced that the reason for that is because the actual mindset is so broad. What happens is people cherry-pick and focus on their favorite parts, or the easiest parts, or the shiniest parts, or the parts that they think will affect their bottom line with the most immediacy.
This results in the word DevOps losing a lot of its meaning.
But when you get back to the whole, broad, mindset, there’s a lot of value here.
My only reservation is that I’m increasingly convinced that speed shouldn’t always be the focus of development. But that’s another conversation.
If you’re a dev or ops person slogging through a terrible organization, putting out fires everyday, read this book. You should also read it if you ever talk about DevOps, or what it means. You might have blind spots.
4.5 stars.
DevOps is a fraught topic. It’s come to mean so many things to so many people. And I’m increasingly convinced that the reason for that is because the actual mindset is so broad. What happens is people cherry-pick and focus on their favorite parts, or the easiest parts, or the shiniest parts, or the parts that they think will affect their bottom line with the most immediacy.
This results in the word DevOps losing a lot of its meaning.
But when you get back to the whole, broad, mindset, there’s a lot of value here.
My only reservation is that I’m increasingly convinced that speed shouldn’t always be the focus of development. But that’s another conversation.
If you’re a dev or ops person slogging through a terrible organization, putting out fires everyday, read this book. You should also read it if you ever talk about DevOps, or what it means. You might have blind spots.
4.5 stars.
lotuseater96's review
informative
medium-paced
4.0
A good primer on various devops practices and strategies. The case studies are especially interesting. Would recommend for any software professional that's looking to enhance devops health in their team.
wiig_with_k's review
3.0
Good, maybe a bit too many examples from the big players for my tastes, but the practices resonate.