The Art of Subtracting
TL;DR: Adding is easy and visible. Removing is harder and invisible. The most elegant systems, in code and in life, are defined by what they leave out, not what they include.
Every engineer I know defaults to addition.
When a system is slow, we add caching. When a process breaks, we add validation. When a team struggles, we add meetings. When life feels out of control, we add tools, frameworks, routines, trackers.
It feels productive. Adding is visible. You can point to it. You made something. You did something.
Subtraction is invisible. Nobody pats you on the back for the meeting you didn’t schedule, the feature you decided not to build, the commitment you declined. But those decisions, the ones where you chose to remove rather than add, are often the most important ones you’ll make.
I learned this the hard way.
There was a period where I was running multiple side projects, maintaining a reading list I never touched, subscribed to newsletters I hadn’t opened in months, and juggling three different note-taking systems to “stay organized.” I was adding more structure to manage the chaos that the previous structure had created.
At some point I stopped and asked: what would happen if I just removed it?
Not reorganized it. Not optimized it. Just removed it.
The answer surprised me. Almost nothing bad happened. A few things I’d been dreading to drop turned out not to matter at all once they were gone. The reading list didn’t need a new app. It needed to be a much shorter list. The note-taking systems didn’t need integration. They needed to be one system.
Subtracting revealed what was actually essential by eliminating everything else.
There’s a concept in engineering called the minimum viable product, the simplest version of a thing that still works. But there’s a parallel idea that rarely gets discussed: the minimum viable life. Not minimal as in deprived. Minimal as in stripped of what doesn’t serve you, so what remains has room to breathe.
The reason subtraction is hard isn’t logistical. It’s psychological. We attach identity to our possessions, our commitments, our busyness. Removing something can feel like removing a part of ourselves. It can feel like admitting we were wrong to add it in the first place.
But that’s not what it means.
Subtraction is not failure. It’s editing. Good writing isn’t about adding more words. It’s about cutting the ones that don’t earn their place. Good architecture isn’t about adding more services. It’s about having exactly as many as you need and no more.
Good living works the same way.
The question isn’t “what can I add to make this better?” It’s “what can I remove so what’s already here gets to be better?”
Action: Identify one thing you can remove from your life this week, a tool, a habit, a subscription, a commitment. Not reduce. Remove. Notice what changes when it’s gone.