the wall of confusion
expressionops culture
The dysfunction where developers and operations hand work back and forth without shared ownership.
Dev throws code 'over the wall' to ops and walks away; ops catches the fallout and blames dev - each side optimizing locally while the whole suffers. Naming the wall of confusion was part of what launched DevOps, whose whole point is to tear it down with shared goals and tooling.
The wall of confusion is the boundary between development and operations, where each side has incentives the other's work undermines. Development is measured on shipping change; operations is measured on stability, and change is the leading cause of instability. The wall is not a personality problem, it is a structural one.
What it produces is recognizable everywhere it exists. Work is thrown over rather than handed over, with no shared understanding of how it runs. Incidents become attribution arguments. Operations builds change-approval processes to slow the flow, development routes around them, and both responses are rational given the incentives each side is actually measured against.
DevOps was named for exactly this, and the useful part of it is the diagnosis rather than the tooling. Shared on-call puts operational pain where the design decisions are made, shared metrics stop the two groups optimizing against each other, and you-build-it-you-run-it removes the wall by removing the handoff. Buying a pipeline tool and keeping the incentives unchanged reproduces the wall with better automation, which is the most common way the idea gets adopted and fails.
Also known as: throw it over the wall, dev vs ops wall