Good overview of many trends over the last thirty years brought together.

Completamente imprescindible para entender la filosofía DevOps. Fácil de leer, con ejemplos de la vida real en empresas que todas conocemos y super didáctico.

A quote from the book “the use of version control by Ops was the highest predictor of both IT performance and organizational performance. In fact, whether Ops used version control was a higher predictor for both IT performance and organizational performance than whether Dev used version control.” says enough … read it at least twice!

This is the most important, useful, influential book I've ever read for work. Anybody who works in a company that uses technology should read this. Being someone who is not from a tech background but has joined a tech team (in a coordinating role), this has given me so much of what I needed to know to meaningfully contribute to the strategy.

This is one of those books that I read for work.
It's not a book to read next to a fireplace while sipping your favorite drink. But I liked it because it was informative and concise. It felt at times like a buzzword bingo and the name dropping seemed a bit excessive, but that's okay. The book tells you what the author think it's important to know about DevOps.

DevOps is an evolution of the Agile process applied to IT operation teams. It basically applies the principles of quick feedback, build-measure learn and applies it to the deployment of software to distributed systems that need to be highly available, secure and robust.

I'm glad I read it.

A must read for it, leadership and devs.

I really liked the content of this book. It’s very instructive. Authors supports their arguments with lots of real life examples which is both inspiring and admirable.

However I really don’t like couple things about the book as well. Let’s start with fonts. They are too small for me to easily follow sentences. My astigmatism is not helping either. I’d appreciate to have 2 volume series with more readable fonts.

The language of the book is too complicated. Even though I have some prior context as a software developer, time to time I found hard to follow up the jargon of the book. Especially the abbreviations. Sometimes I even forget where they were originally given if they have been given. It would be nice to have them in place repeatedly so that we are not distracted by the action of searching them.

Those being said, I think this is still a very valuable addition to my library. I’d definitely revisit it time to time. However let me put it honestly, it’s not an easy read if you want to read it cover to cover. It’s one of the reference book that you would like to revisit it again.

Best introduction to devops philosophy and practice

Thanks to the book club for helping me slog through this.