What do you think?
Rate this book
Next Gen DevOps: Creating The DevOps Organisation
The indispensable guide to building, launching and managing online services in the 21st century. Next Gen DevOps: Creating the DevOps organisation is a management guide for IT professionals and executives, in businesses large and small, that describes how the organisational paradigms of the last 60 years are unsuited to the modern business of combining SaaS, Clouds and DevOps solutions to create robust and successful online services. Now updated to include an examination of the DevOps industry leaders and a detailed guide to the Next Gen DevOps framework to help guide your business through it's transformation journey.
228 pages, Kindle Edition
First published September 25, 2014
4 people are currently reading
33 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 3 of 3 reviews
January 12, 2016
Not too terrible. A bit "deliberate." By that, the tone of writing is very a-matter-of-fact, almost as if the writer was directing mental energy towards convincing the reader of the validity of his premises vs. writing in a expository manner detailing what this particular DevOps book is about. "Code was written. Tests implemented. Fatigue avoided." It got to be a bit irksome at times.
The "product-based" mentality appeals greatly to me, since it will avoid the "toss your shit-riddled codebase over the wall to the Ops team and call it a day" occurrence. Still, felt that this could have been more succinctly summarized. The books organization is OK, but hours and hours of reading made it hard to clearly delineate distinctness between the ideas in one chapter to another, to the point that every chapter felt needlessly redundant.
I could be a bad reader, since I want someone to "tell me what I should do." The suggestions and ideas are great, but may suffer from the harsh reality of people in mid-to-large organizations wondering how they should go about telling everyone they are doing it wrong and that our org structures are based on 18th century manufacturing practices (which they are). Describing this Next Gen Devops feels divorced from the tangible political context that employment in IT occupies. It may be that the person to read this should be execs who can implement these concepts by fiat.
Still, testing, ops, and dev interweaving their divergent skills sets into a product-based approach to systems and software == hotness. The historical differences elucidating the split between ops and dev probably was a bit longer than it needed to be, but valuable to internalize.
A decent book, but maybe not the best. Also, if I read the word "dependant" as I have read in this book one more time, I will probably stick a pencil in my eyeballs. A better editing job could have been done to avoid these sorts of things.
The "product-based" mentality appeals greatly to me, since it will avoid the "toss your shit-riddled codebase over the wall to the Ops team and call it a day" occurrence. Still, felt that this could have been more succinctly summarized. The books organization is OK, but hours and hours of reading made it hard to clearly delineate distinctness between the ideas in one chapter to another, to the point that every chapter felt needlessly redundant.
I could be a bad reader, since I want someone to "tell me what I should do." The suggestions and ideas are great, but may suffer from the harsh reality of people in mid-to-large organizations wondering how they should go about telling everyone they are doing it wrong and that our org structures are based on 18th century manufacturing practices (which they are). Describing this Next Gen Devops feels divorced from the tangible political context that employment in IT occupies. It may be that the person to read this should be execs who can implement these concepts by fiat.
Still, testing, ops, and dev interweaving their divergent skills sets into a product-based approach to systems and software == hotness. The historical differences elucidating the split between ops and dev probably was a bit longer than it needed to be, but valuable to internalize.
A decent book, but maybe not the best. Also, if I read the word "dependant" as I have read in this book one more time, I will probably stick a pencil in my eyeballs. A better editing job could have been done to avoid these sorts of things.
March 5, 2015
The premise of the book, as I've understood it of course, is that Development and Operations might once have been separate operational silos, but that is no more. Technology and business practices mean there is a tight coupling between the two and that needs to be understood.
A point to comment on - reading through Smiths book I took it as half explanation about DevOps and half a reflection and exposition of what companies do wrong. At times it is easy to forget you have a DevOps book in your hand and instead it reads more like a management handbook. No matter what your field, if you're worked for a reasonable sized business, this part of the content will resonate with you. However, as with his exposition of the path of technology development that saw DevOps arise, Smith skilfully brings the book back around to the core topic and shows how it impacts DevOps. Within the book he then proposes a model for what DevOps could look like going ahead.
It's evident Smith has much more to say on his field and I look forward to reading more from him in the future.
Mark.
A point to comment on - reading through Smiths book I took it as half explanation about DevOps and half a reflection and exposition of what companies do wrong. At times it is easy to forget you have a DevOps book in your hand and instead it reads more like a management handbook. No matter what your field, if you're worked for a reasonable sized business, this part of the content will resonate with you. However, as with his exposition of the path of technology development that saw DevOps arise, Smith skilfully brings the book back around to the core topic and shows how it impacts DevOps. Within the book he then proposes a model for what DevOps could look like going ahead.
It's evident Smith has much more to say on his field and I look forward to reading more from him in the future.
Mark.
Read
September 19, 2016Location: GG7 IRC
Accession No: DL028489
Accession No: DL028489
Displaying 1 - 3 of 3 reviews