We tend to focus on addition. Ship the feature, add the page, +1 the competition. It’s because addition is legible. 1 + 1 = 2 and you can point at the thing added. Subtraction is invisible. If I do 1 - 1 = 0 the result is the absence of what was once there. Addition demos itself and subtraction needs a witness to testify.
The strongest things I’ve made got that way by removal. A service runs faster with tighter logic. A deck gets sharper when a slide leaves. An interface has less clutter when a panel dies.
Deleting is hard to do
Deletion feels like loss because effort is sunk into the thing being cut. Stakeholders never see effort, they see the result and the result is lighter without it. The cost you paid to make the thing is not a reason to keep it.
Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.
It’s a cliché because it’s load-bearing. The discipline isn’t knowing the quote but being willing to delete something good because something else is better, and two goods competing for the same attention leave you with neither.
A practical rule
When something you made feels off, don’t ask what’s missing. Ask what could leave without anyone noticing. Cut that first. Then look at it again. The thing that was actually wrong is usually easier to see once the clutter around it is gone.
This site is an argument in the same direction: no framework where none is needed, no card grid where a list will do, no dashboard where an inbox already lives in everyone’s head.