> In most cases, the business cannot afford to stop all feature work in this way, and so the problem will persist forever, becoming a permanent drop in producti

> In most cases, the business cannot afford to stop all feature work in this way, and so the problem will persist forever, becoming a permanent drop in productivity. It will also make your developers miserable. This scenario is only possible if the project has no automated testing or invests any effort in QA or no one pays any attention whatsoever to whatever is running in prod. Meanwhile, one of the basic features of CICD is automated rollbacks. If this sort of problem happens on a project, the problem was not caused by a developer having a bad day. The problem is caused by an entire team enduring a culture that allows problems to fester without anyone doing anything about it.