(Pdf) Effective Devops by Jennifer Davis – Book, eBook or Kindle ePUB free

FREE DOWNLOAD Effective Devops

Egies you can use to engineer sustainable changes in your environment regardless of your level within your organizatio After first 100 pages I already want to throw it away It mentions so often the word bias I started to have a bias for this word Fortunately it has also good advices I will keep reading it but for the moment just 2 for repeting to every few pages about the rasialsexual problems of some people

READ & DOWNLOAD æ EXCEEDBDF.CO.UK Ý Jennifer Davis

Effective Devops

This practical guide addresses technical cultural and managerial challenges of implementing and maintaining a DevOps c This book has two problems first they don t define DevOps second they don t define the target audience As a result while the book contains a lot of interesting content it s arranged in a way that makes it very difficult to learnNow you might argue but wait they do define DevOps right in Part 1 OK let s look at their official definitionDevops is a cultural movement that changes how individuals think about their work values the diversity of work done supports intentional processes that accelerate the rate by which businesses realize value and measures the effect of social and technical change It is a way of thinking and a way of working that enables individuals and organizations to develop and maintain sustainable work practices It is a cultural framework for sharing stories and developing empathy enabling people and teams to practice their crafts in effective and lasting waysOK close your eyes and tell me what did that paragraph say It s hard to repeat isn t it That s because their DevOps definition is vague and deliberately avoids any concrete details If I remove the word Devops from that paragraph above it could be about anything The rest of that first part makes you feel like you re trying to hold on to a slippery fish they spend a ton of time defining what DevOps is not repeating dozens of times there is no one true DevOps and actively dodging and denying any concrete details to the point where no matter how much you try you can t grasp it They even acknowledge this fact in the book itselfThere has been some discussion in the devops community as to whether or not devops has lost its direction Critics of the movement say that it is too defined by negative spaces by people saying what devops isn t rather than what it is or not providing a concise definition for it at all Yup I am one of those critics It seems like the authors attempted to be as all inclusive as they could be but the result is that this isn t a book about Effective DevOps but rather a haphazard collection of things the authors believe lead to Effective Companies And while one of the goals of DevOps is to make a company effective you can t really claim that everything that makes companies effective should be put under the umbrella DevOps Their definition is too broad and as a result the message of this book is very dilutedIt s also diluted in the sense that the book tries to speak to a bunch of different audiences Some parts are targeted at developers some at operations people some for managers some for HR some for the CEO some for the legal team Depending on who you are you ll find a few parts interesting and the rest will feel largely irrelevantI ll also mention that while the book talks a lot about avoiding unconscious biases it falls to some itself For example one is the odd stereotype that a 10x engineer is always a 10x asshole that no one wants to work with The real 10x engineers are 10x precisely because others love working with them and are productive as a result Another one is the assumption that the differences between tools eg programming languages cfg mgmt systems etc don t matter All that matters is how you use the tools It s certainly true that with the wrong workplace culture even the best tools will be ineffective But the opposite is not true even the best culture won t succeed with the wrong tools There is a reason Etsy isn t written in assembly there is a reason you use a config mgmt tool like Chef or Puppet and not manual shell scripts there is a reason you store data in an RDBMS like MySL and not flat text files There is a right tool for the job and it s worth the time to find itAll of this is a shame as there is some excellent content lurking in these pages There are great discussions of diversity and minorities in tech organizations The authors could extract those discussions go into detail and turn them into an great standalone book focused on that one topic The case studies scattered throughout this book are intriguing too as they contain real world stories with concrete details of how DevOps actually works Again the authors could extract those stories go into detail and create yet another interesting standalone book on DevOps stories Chapter 18 has lots of interesting stories about promotions transparency evaluating organizations and cultural debt what an awesome concept Again a standalone book on Cultural Debt would ve been a great readBut as it is all of this intriguing content is crammed into a single book organized poorly and only explored at a surface level As always I jot down interesting uotes as I read Here are some of the best ones from this bookThere is a sea change happening in software development and operations and it is not simply the introduction of a new word into our lexicon it s much than that It is a fundamental shift of perspective in the design construction and operation of software in a world where almost every successful organization recognizes that software is not something you simply build and launch it is something you operateIf someone isn t on the right track with something that they re doing waiting up to a year for their next annual review isn t good for anyone involved They will likely go through this time thinking they are doing well leading to a nasty surprise come review time The psychology of getting feedback shows that people generally react to these sorts of negative surprises emotionally rather than intellectually a phenomenon known as amygdala hijacking As a result people are less likely to fully understand and be able to act on the feedback they are being givenOne of the differentiating factors between a group and a team is the presence of trustJames Stewart director of technical architecture at GDS recounted the general approach for tool selection shown in Figure 14 4 via a uote from JP RangaswamiFor common problems use OpensourceFor rare problems use BuyFor uniue problems use BuildDisallowing remote work reflects a culture that values the appearance of doing work than the effectiveness of the actual work

Jennifer Davis Ý 1 READ & DOWNLOAD

Ulture by describing failures and successes Authors Katherine Daniels and Jennifer Davis provide with actionable strat The book draws a clear line between what is tooling processes and what is actually devops cultureIt makes you think about the usefulness and goals of processes and tools to build a devops culture rather than just throw a bunch of buzzle words about devops world Sometimes it is easy get lost in this sea of newcrazy methodologies and forget why we do things and its essenceIt also addresses the affects and conseuences that a blameful culture will cause and how avoid this kind of situation Besides that it also touches a delicate subject inside companies where developers have prestige than others employees and how harmful it can be In addition the book also talks how a rock star culture might not be the right track and how it can be inefficient for the company as a whole


10 thoughts on “Effective Devops

  1. says:

    This book has two problems first they don't define DevOps; second they don't define the target audience As a result while the book contains a lot of interesting content it's arranged in a way that makes it very difficult to learnNow you might argue but wait they do define DevOps right in Part 1 OK let's look at their official definitionDevops is a cultural movement that changes how individuals think about their work values the

  2. says:

    Decent book Think some folks were put off by many of the soft skill items mentioned at the beginning of the book

  3. says:

    Full disclosure i'm a personal friend of the authorThis book is an excellent read for anyone who wants to learn about devops and about how to improve computer operations in generalOne important thing this book really emphasizes is how important it is to create an inclusive workplace As a white male it`s easy for me to assume that there isn'

  4. says:

    Some of the observations were spot on and show me new way of understanding things that are going on at our company The stories helped to explain presented ideas I would maybe enjoy it even if it was shorter D probably due to parts that i didn't find so interesting Overall I'm happy that I came across it and would recommend it to everyone working in IT

  5. says:

    The book draws a clear line between what is tooling processes and what is actually devops cultureIt makes you think about the usefulness and goa

  6. says:

    An excellent book on how to build a inclusive culture adapted to the pressure of devops work

  7. says:

    Focusing on the Culture of DevOps Effective DevOps is a welcome addition to the literature on modern software development practice It is a rare book in the field that begins with people and process then moves to technology The co authors have anchored considerations of effectiveness in a broader social science perspective that I found very

  8. says:

    After first 100 pages I already want to th

  9. says:

    It took me a while to get through this book Rather than laying out some good information on how to effectively build out a Devops organization it seemed to be like the annual workplace sensitivity training that one takes at most large organizations

  10. says:

    Good and broad primer for anyone wanting to start Wide array of topics that are important for a successful implementation

Leave a Reply

Your email address will not be published. Required fields are marked *