The Case for Doing Less with Software
0.100 USDC (1)Defaults are never neutral—they are arguments about how work should be done. The real problem is that we adopt them without examining the assumptions behind them.
Defaults are never neutral—they are arguments about how work should be done. The real problem is that we adopt them without examining the assumptions behind them.
Tools don't change your work, they change your attention. A reflection on why defaults—in software and in the mind—teach us more than customization ever will.
A watchlist of protocols with running code, rough consensus, and the quiet ambition to become infrastructure defaults.
The tools we use every day are shaped by invisible decisions—defaults chosen by designers we'll never meet. This essay explores the quiet craft behind those choices, from the blink of a text cursor to the privacy settings that can change lives, and asks what it means to design for people who rarely
Camera defaults aren't obstacles to fix on day one — they're hypotheses about light worth testing for months before you overrule them.
Defaults are the invisible architecture of our days, shaping behavior without our consent. By examining the tools we use, we can reclaim agency and make our choices intentional.
Embrace a beginner's mind to see beyond camera defaults and unlock your unique photographic vision.
Every tool arrives with a default, and that default is a kind of argument. This field guide is about noticing the ones you never chose.
You do not need better tools; you need fewer open questions. Assigning defaults to repeated decisions is the cheapest way to buy back attention.