I would love to see that article. That isn't surprising in the slightest to me. Just a quick nitpick. A bad config more often than not in my experience is open

I would love to see that article. That isn't surprising in the slightest to me. Just a quick nitpick. A bad config more often than not in my experience is opening up a code path that is riddled with bad code, whether it was not vetted with the proper testing or the wrong environment. But to your point, I think most people would agree that configuration changes are almost never reviewed with the granularity of a code change. Yes, we may do our due diligence with an approved PR and vetting the configuration and testing the change before deploying it. But, reviewing a PR with a bad config change in json or yaml doesn't necessarily tell you about the code paths that it will open up which makes it much harder to reason about the consequences that a potential bad config push would do. We should always be reflecting about how adding knobs (configuration) to our programs greatly increases the complexity of the service.