To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyses reviews to verify trustworthiness.
A great overview of modern DevOps practices, covering at a high level what a modern development workplace "should" be doing. Well organised and very readable, which can't always be said for technical books.
It can come across as a bit buzzwordy and sales-pitchy at times - I'd prefer to never again have to read either of the phrases "optimising the value stream" or some variation of "those who adapt these practices will succeed in the marketplace at the expense of those who don't". At a certain point the authors need to accept that either they've sold the reader on the concept or not, and just cover the concept that they're introducing.
I get that it's the concepts that are important and not the tools, but I would have appreciated an occasional breakout deep dive into the details of what someone did with tool X in order to accomplish objective Y. Those are lightly brushed on - example tools for accomplishing a given objective are listed, and there are case studies throughout - but they're often very evangelistic ("Etsy did X and optimised their value stream!") without the warts and all technical details. To be fair, there's an "additional resources" section in the back that points to more technical resources.
Perfect companion to the Phoenix Project (as it shares one of the same authors and is more of an entertaining 'horror story with a happy ending' about how badly managed IT projects can fail!) which I also bought at the same time. Agile infrastructure and lean IT, in the future people will look back on the history of IT management and DevOps and wonder how and why we ever delivered infrastructure and software projects using individual team silos, just throwing barrels of code down the waterfall without talking back to whoever started throwing them! If you really want to get ahead, start with the third section for practical implementation advice.
Este libro concentra a cuatro "estrellas del rock" de DevOps: Patrick Debois (creador de los DevOpsDays), Alspaw (pionero DevOps en Flickr), Kim (autor del Phoenix Project) y Humble (autor de Continuous Delivery).
El contenido del libro, muy influído por la aplicación del "Lean Thinking" a los departamentos de IT, está vertebrado en las "tres vías" que ya aparecían en el Phoenix Project: 1) Principios del flujo 2) Prácticas técnicas de feedback 3) Prácticas técnicas de experimentación y feedback
Es un libro completo y bien explicado, con muchos ejemplos, que permite entender DevOps como transformación de la organización IT, más allá de la automatización de los despliegues y de la infraestructura. Mi crítica principal es que ignora demasiado el movimiento "Agile" del desarrollo de software, para centrarse casi exclusivamente en Lean. Esto supone una cierta deformación de la realidad histórica que condujo a DevOps, que hereda mucho más de Agile que de Lean. Salvo esto, un libro estupendo.
This book is filed with insights into the practice of Developments & Operations in software companies. It is light on telling you how to achieve the desired results, and big on stating in fancy language what the desired results of a DevOps Engineer ought to be. One downside, mentioned above, is that there's a lot of fancy language (adjectives that basically say, "do things the best way"), and sometimes it feels like the language borders on marketing material for creating a niche in the field of software development. Like someone is trying to convince us that we need to integrate Dev and Ops in organizations. Maybe that's because it's a bit of an older book, and it laid the foundation for the modern practice of DevOps. In any case, it's an excellent intro, and I would recommend the read.