My last post discussed the danger of programming in YAML, with examples from the CI domain, where YAML is the norm for defining delivery pipelines. Worse still is YAML programming at scale. As services multiply, so do the YAML files, and so does duplication and drift. This holds us back.
Proliferation, Duplication, and Drift
Consider Microsoft’s GitHub organization. To ensure an apples to apples comparison, I focused on one CI tool (Travis) and one stack (Node).