A brilliant solution nobody understands is an operational liability.
A solution is only complete when the team can safely change and operate it.
Interpretation
Local cleverness can create organizational fragility. If only the author can debug a design, every incident and change waits for one calendar. Prefer an approach the team can explain, observe, and maintain. When complexity is necessary, invest equally in teaching and operational support.
Practice
- Ask another engineer to explain the design back.
- Provide operational examples and failure modes.
- Choose familiar tools unless novelty buys measurable value.
Anti-pattern
Merging an ingenious subsystem because its author promises to own it forever.