Read Online Summary Analysis Review of Gene Kim Jez Humble Patrick Debois John Willis the Devops Handbook by Instaread Instaread 9781683785934 Books

https://images-na.ssl-images-amazon.com/images/I/51FmFULiadL._SX311_BO1,204,203,200_.jpg

Product details Print on Demand (Paperback) Publisher Instaread (November 23, 2016) Language English ISBN-10 1683785932

Summary Analysis Review of Gene Kim Jez Humble Patrick Debois John Willis the Devops Handbook by Instaread Instaread 9781683785934 Books Reviews

• The DevOps Handbook is directed at tech company manages trying to solve the dilemma of how to get their development people to synch their efforts with their operations people in putting together a solid effort in delivering their tech products to the marketplace. This seems an esoteric topic directed at the few, but actually there are lessons to be learned for anybody interested in developing cooperation between disparate departments in any company or organization.
  
  This Instaread summary does an excellent job os putting al this into plain English, and with it's excellent key takeaways of the most important points. I think this book would also work for small tech companies, and even companies that provide services to tech companies. Well-written, and definitely an excellent companion read to the full book. I highly recommend it.
• The DevOps Handbook by Gene Kim, et al is a manual for technology companies, designed to help them develop procedures, primarily integrating the development and operations elements of their organizations, to deliver high-quality, high-value products to their consumers. The techniques outlined in the book can also be applied by other than IT enterprises.
  Instaread’s Summary, Analysis & Review of the book is an in depth inside look at the main themes, with an analysis of the book’s key takeaways. With just 15 minutes or less reading, you will have a thorough understanding of this book’s contents and value to you as a reader. This brief Cliff Notes book overview is a handy tool for developing your short list of books to purchase.
• Does anyone remember Cliff's Notes? This is sort of like them but on Performance Enhancing substances. This is a very condensed (but effective) version that brings a lot more to the table than I anticipated.
  
  Frankly, I admit to thinking this was a bit "gimmicky" but the details involved are substantive and I come away with a fairly workable knowledge of the gist of the book without having to spend a LOT more money and a considerable amount of time to read through all the potential fluff. Additionally, this is a great barometer that lets me know whether or not I should spring for the entire book instead of spending way more money than anticipated to find nothing of value.
  
  As for this instance, I like how it lays down the foundation concerning development and operations and how a lack of communication between the two can lead to very negative results and a unnecessary struggle whereas devops working together can be a rather symbiotic relationship.The crux of the argument focuses on the story of Toyota and the change in culture they cultivated.
  
  This contains extremely specific results and appear to have a lot of work put into it (more than I would ever want to do as it would not be a fun week for me...give or take).
• Let me begin this review with my reasoning for only rating this summary with 3 stars. I read this summary with no prior knowledge on DevOps. I had a hard time following along, not because it was poorly written, but because I just had no clue what I was reading about. As I read through the summary, I did start to have a very, very brief understanding of DevOps, but it just didn't stick with me.
  
  According to Wikipedia, "DevOps (a clipped compound of development and operations) is a term used to refer to a set of practices that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals while automating the process of software delivery and infrastructure changes."
  
  This summary would benefit a person who owned a company or managed a business that was looking for a way to bridge the gap that often exists between development and operations. So the DevOps business model would help a business improve efficiency. Personally, I think I would need to read the full version of the title in hopes that I could gain a better understanding of the business plan; however, a person who was considering DevOps and just wanted a brief overview before really researching the model would most likely enjoy this summary. I don't think that I would solely rely on this summary to obtain a full understanding of DevOps though.
  
  I did, however, think the summary was well-organized and full of pertinent information. I just needed a little more to really take something solid away from it.
  
  Note This is NOT a full version of the publication. It is a summary that contains the main points of the title. I received a complimentary copy of this summary in exchange for my honest opinion.