Casus Belli Engineering: When a broken feature becomes an excuse to tear everything down

The thesis

Marcos Magueta argues in a recent blog post that software organizations often resolve crises the way ancient societies did: by finding a scapegoat. He borrows René Girard’s anthropology and a stark Aztec analogy to show how a single visible failure can collapse trust in an entire system. The emotional heart of the piece is simple and sharp — people don’t separate feature from foundation; once confidence is lost, everything looks rotten. Ouch. Seen that in your org? You’re not alone.

The mechanism

Magueta calls the tactic "Casus Belli Engineering": the deliberate use of perceived failure as a pretext to replace working systems with preferred alternatives. It has been reported that some actors allegedly manufacture or amplify crises so they can justify ripping out dependencies, architectures, or codebases that stand between them and their preferred direction. The scapegoat must be close enough to the failure, defenseless (old, unfashionable, or championed by gone colleagues), and — critically — replaceable with what the accusers want. Ritual condemnation follows. Repetitio. Performance. Done.

Why this matters

This isn’t just academic. In an industry addicted to rewrites, shiny frameworks, and triumphant origin stories, the pattern converts technical friction into political power. The real loss is social: people stop trusting systems and each other. The fix is boring but essential — better root-cause work, clearer incentives, and an awareness that not every outage is a moral failing. Without that, teams will keep burning codebases to keep the peace. Who benefits? Ask yourselves.

Sources: marcosmagueta.com, Hacker News