> As a tech lead I see my primary contribution as saying “no” to features that co-workers think are important but can’t justify. The real trick is knowing when

> As a tech lead I see my primary contribution as saying “no” to features that co-workers think are important but can’t justify. The real trick is knowing when a new feature adds linear complexity (its own weight only) or geometric complexity (interacts with other features). Both should be avoided, but the latter requires extra-convincing justification. https://www.teamten.com/lawrence/writings/norris-numbers.html https://www.teamten.com/lawrence/writings/norris-numbers.htm... The main tool is to come up with a neutral system for measuring the complexity of a proposal, and then use benign punitive measures like "whoever broke the build has to bring donuts in the morning" to reinforce that the team favors boring stability over fragile complexity.