This book is sitting in our office. Is it actually a good read? Its very dusty so I always wrote it off as just another corporate book.
It basically created "Devops" as a mindset. You decide if thats a good or bad thing.
Id personally call it a good book. The first half will hurt you if youve ever worked as a sysadmin, as it basically recreates all the worst parts of the job at once to setup the story, but the second half explains how devops as a thought process can solve the issues it creates. It does not going into tools, just methods and concepts.
It can help you fix your orgs bullshit. It is heavy on "you need management buyin" angle though, so if you cant get that at your job, continue to abandon all hope.
This book is sitting in our office. Is it actually a good read? Its very dusty so I always wrote it off as just another corporate book.
It basically created "Devops" as a mindset. You decide if thats a good or bad thing.
Id personally call it a good book. The first half will hurt you if youve ever worked as a sysadmin, as it basically recreates all the worst parts of the job at once to setup the story, but the second half explains how devops as a thought process can solve the issues it creates. It does not going into tools, just methods and concepts.
It can help you fix your orgs bullshit. It is heavy on "you need management buyin" angle though, so if you cant get that at your job, continue to abandon all hope.
I enjoyed it.