If the DevOps movement has gained more and more momentum over the past few years, it is because we have understood that two forces contradict each other in the development and maintenance of applications. On the one hand, we want to deploy new features to satisfy or acquire new customers while keeping an eye on the unintended consequences that the introduction of new features can have on our codebase. On the other hand, we want to stabilize what we already have to capitalize on what we have learned from past mistakes and improve it. Intuitively, we associate the first objective with development teams, and the second one with infrastructure teams, hence the subsequent drifts and misunderstandings that arise between teams. To avoid this pitfall, we have no magic solution, but we are convinced that these two objectives must be carried in the same way by everyone.
