Arbeiten auch Sie nach DevOps-Prinzipien? Sollen oder wollen Sie umstellen? Was ist wichtig? Worauf kommt es an? Das Ziel von DevOps ist, dass Softwareentwicklung und IT-Auslieferung Hand in Hand arbeiten. Das ermöglicht schnellere Release-Zyklen und schont die Ressourcen. Wie das im Einzelnen geht, zeigt dieses Buch. Es stellt eine Roadmap für die Umstellung zur Verfügung, nennt notwendige Management- und Technologie-Entscheidungen und -Tools und scheut auch nicht davor zurück, notwendige Unternehmenskulturänderungen zu benennen, damit der Sprung ins DevOps-Gewässer gelingt.
📌Changes should be simulating, not stressful. 📌Unlike simple, linear systems, the code and infrastructure we operate and maintain are incredibly complex. A single "root cause" simply does not exist. The failure is the result of pf multiple actions in the system, so it would make more sense to look for "sources of failure". 📌Everyone is accountable, but not everyone is an owner. And my favourite one: 📌Increasing velocity requires optimizing performance while respecting the constraints and context the team experiences daily. (Longer working hours could not do much here😉 )
Bringing more light into DevOps mindset author covered so many vital points for every organization, that give my vote this being one of the greatest IT books in 2019!
There are some helpful and interesting things here, but also unaddressed contradictions and also some profoundly bad advice mixed in. For example, this book says to promote work life balance for your employees, but also says engineers who resist being on call are an indication of a cultural problem.
It also claims to value diversity, but encourages any team member (not just a supervisor) to address performance or behavior issues perceived in new employees. To me, this feels like a great recipe for building an abusive monoculture.
While the author clearly has a lot of valuable experience and there is a lot to learn here, the thought of working at a company she runs or where leadership read her book uncritically makes me feel physically ill.
I’m admittedly biased (Emily is a friend and was kind enough to mention me in the acknowledgements), but this is an excellent overview of getting started on your devops journey. From learning how, what, and why we measure; to how to find small wins; to finding champions for this cultural shift, this book covers it all.
This book was slow to read. It took me a while to get into it and finish reading it. The concepts are great and helped me understand DEVOPS a little better.
Thoroughly good and enjoyable. Maybe some of the technical sections will date with time, but as a philosophy I can see this book being in my work library for years to come.