The best infrastructure demo is usually a disappointing one. The deploy completes. The graphs barely move. Nobody opens a heroic incident channel.
We are drawn to clever systems because cleverness is visible. It makes for a good diagram and a satisfying conference talk. Reliability is quieter. It shows up as an uninterrupted afternoon, a small diff, and a new teammate who can ship without a guided tour of every scar in the system.
Boring is an outcome, not an ingredient
A boring system may have sophisticated machinery underneath it. The point is not to avoid complexity at all costs. The point is to absorb necessary complexity so the people using the system do not have to carry it around in their heads.
Spend novelty carefully
Every unusual tool asks the team to learn a new language. Sometimes the payoff is worth it. Often, the established option leaves more attention available for the problem that is actually unique.
The goal is not a stack with no personality. It is a stack whose personality does not wake anybody up at 3:17 a.m.