Nobody Gets Promoted for Simplicity

The post argues that engineering systems often reward complexity over simplicity. In interviews, design reviews, and promotions, overbuilt solutions create a stronger story than the simplest thing that works, even when the simpler path is better.

It also says complexity is sometimes necessary, but unearned complexity should be avoided. Engineers and leaders are urged to make simple decisions visible, document the judgment behind them, and change review and promotion incentives so clean solutions count as real impact.

Reading notes

#

• Complex solutions tend to look smarter in promotion packets and design reviews than simple ones.
• The engineer who ships the simplest working feature can end up with almost nothing to say about the work.
• Interviews can teach candidates that a simple answer is not enough, which pushes them toward unnecessary complexity.
• Design reviews often pressure engineers to future-proof too early by adding layers and abstractions.
• The problem is not complexity itself, but complexity added before it is needed.
• Seniority is described as knowing when not to use extra tools and patterns.
• Engineers should describe the judgment behind simple work so the decision not to build something also becomes visible.
• Leaders should ask what the simplest shippable version is and what signals would justify adding more complexity later.
• Promotion discussions should recognize when someone avoided unnecessary systems, not only when they built large ones.
• What a team celebrates publicly shapes what people will optimize for.