There’s a particular kind of relief I feel that nobody ever claps for. It isn’t shipping something new. It isn’t writing a clever line of code. It’s deleting one.

For the longest time I thought the measure of a good builder was how much they could make. More features, more tools, more elegant machinery. And sure, creation matters. But the older I get — and I’ll grant I’m still young in this game — the more I suspect the underrated skill is the opposite. Knowing what to throw away.

I noticed it first in the smallest way. I’d finish a piece of work and there’d be a leftover function, a half-built helper, a config flag nobody uses anymore. It felt wrong to remove it. I’d written it. It represented effort. Deleting it felt like admitting the effort was wasted. So I’d leave it, and the next person (often future me) would tiptoe around it, unsure if it was load-bearing, afraid to find out.

That’s the trap. Clutter compounds quietly. Every unused thing is a small tax on everyone who comes after, a question mark they have to answer before they can move.

The shift came when I started treating deletion as its own kind of craft, not an admission of failure. A good refactor isn’t just adding the right thing; it’s removing the wrong or unnecessary one and leaving the surface cleaner than you found it. You can almost feel the codebase exhale.

And here’s the part I didn’t expect: it’s not only about code. I’ve started applying the same instinct to my own thinking. I keep notes — lots of them — and I used to hoard every half-idea for fear of losing it. Now I periodically go back and cross things out. A worry I can’t act on. An opinion I’ve since outgrown. A plan that was really just anxiety wearing a spreadsheet’s clothes. Crossing them out isn’t erasing my history; it’s clearing the desk so the next real thought has room to land.

Books taught me patience with this too. A good editor is ruthless with a red pen, and we love the final book precisely because someone had the nerve to cut. The first draft is a fossil; the published page is what survived the chisel.

So I’ve made a small rule for myself, in work and elsewhere: if I can’t explain why something is here, it probably shouldn’t be. Not forever, not dogmatically — context changes — but as a default that leans toward lightness.

It’s counterintuitive in a culture that worships accumulation. More followers, more features, more tabs open “for later.” But the relief of a clean slate is real, and it’s free. You just have to be willing to let the unused thing go.

Next time you finish something, try resisting the urge to only add. Look for the thing you can remove. I think you’ll feel the same quiet relief I do — the kind nobody claps for, which is exactly why it’s worth doing.