On Tools That Disappear
A commentary on Ginger Bill's "Good Tools Are Invisible" — why the best tools are the ones you don't notice, and why that's harder to accept than it sounds.
Ginger Bill published an essay this week called Good Tools Are Invisible. It hit #10 on Hacker News with nearly 400 points and spawned almost 200 comments. If you haven't read it, stop and go read it — it's short, sharp, and worth your ten minutes.
What the essay gets right
The core argument is simple: a great tool is one you don't notice. When a hammer fits your hand, you don't think about the hammer — you think about what you're building. When your editor doesn't fight you, you think about code, not keybindings.
The trap Ginger Bill identifies is the one every engineer has fallen into at least once: treating a tool's friction as a puzzle to solve. There's a genuine dopamine hit in configuring neovim just right, tweaking your dotfiles, or winning an argument about tabs vs. spaces. But that feeling — the satisfaction of mastering the tool — is categorically different from producing output. They feel the same in the moment. They are not the same.
> Feeling productive and being productive are not the same thing.
That's the line that should make a lot of us uncomfortable.
The identity problem
The part I kept thinking about after reading it is the identity angle. When you've spent years becoming "the Emacs person" or "the Arch Linux person," you've baked the tool into who you are. At that point, admitting the tool has real flaws feels like admitting you have flaws.
This explains so much of the baffling energy in tool debates. Nobody gets that heated about hammers. But watch what happens when someone says VS Code is fine, actually. The reaction isn't about the software — it's about identity.
Ginger Bill's point is that this identity investment is a trap even when you're right about the tool being good. Because the time you spend defending it, configuring it, and deriving satisfaction from using it well is time you're not spending on the thing you supposedly picked the tool to help with.
What I'd add
The essay is right that invisible tools win. But I think there's a nuance worth naming: "invisible" is personal, not universal.
Vim is invisible to the person who's used it for 15 years. To a beginner, it's a brick wall with a cryptic :q! painted on it. A tool's invisibility is earned through familiarity, and what's friction for one person is flow for another.
The practical takeaway isn't "use the simplest tool" — it's "use the tool where your friction is lowest." And be honest about what that tool actually is, not what you wish it were, not what signals membership in the right tribe, not what makes for a good story.
Read the original
Go read Ginger Bill's essay: Good Tools Are Invisible
It's the kind of piece that sticks with you. You'll find yourself noticing — or not noticing — your tools differently afterwards. And that's kind of the point.