Chapter 96. Empathy as Code
Nirmal Mehta
One of the many reasons for the rise in popularity of cloud computing and DevOps is in response to the established ineffective tension between development and operations teams seen across most of the enterprise IT landscape. The often dysfunctional pattern of a throw-it-over-the-fence approach to responsibility created an environment in which any change was often met with fear and resistance.
I hope to provide some context for all the technologies, tools, architectural patterns, techniques, and other material you are absorbing in this book. I also encourage you to utilize infrastructure as code as common ground between developers and operators.
Empathy as Code
Many of the tools and techniques in this book are centered around writing code that defines and implements various aspects of the infrastructure you are working on; this is commonly known as infrastructure as code (IaC). Whether they’re Terraform modules, Dockerfiles, Ansible playbooks, or Kubernetes YAML/Helm charts, these pieces of code codify decisions that are being made by cloud engineers to dictate what the infrastructure should be to run the developers’ applications.
In addition to the benefits of automation, repeatability, and security that these IaC elements provide you as a cloud engineer, they can also be used to bridge the gap ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access