Faster and cheaper doesn’t always mean better
At some point in the evolution of DevOps, and seemingly out of nowhere, we have become a culture that cost-justifies everything. In doing so, we violate the classic axiom that you can only ever satisfy two of three constraints: scope (quality), time (speed), and cost (low cost). This is known as the project management triangle or the triple constraint, which suggests that any change in one of these three constraints will inevitably affect the others; you will have to pick two of them and compromise on the third. All too often, we introduce some new tool and attempt to persuade others about how it will speed things up, result in cost savings, or free up our time for more meaningful tasks. Then, we’d discover how this new tool could improve quality if we extended it by adding yet another new feature or capability with the promise that it would yield a more reliable process compared to the existing one:
