Every tool is an argument. A hammer argues that problems want force. A checklist argues that problems want process. A tool you love argues so quietly that you stop noticing it’s arguing at all — you just start thinking the way it wants you to think.
The habit loop of software
I noticed this first with my editor. The snippet system was so good that I stopped reading libraries’ documentation. Why would I? Muscle memory filled in whatever the docs would have taught me — except it filled in last year’s API, and the bugs that came from that were subtle and mine.
The tool didn’t fail. It succeeded too well at the wrong thing.
Good tools, honestly
None of this is a case against tools. Good tools are the closest thing we have to leverage:
- A good editor makes the cheap thing easy, which lets you afford the expensive thing.
- A good notebook (this blog, for me) makes thinking feel unfinished until it’s written down.
- A good linter is thousands of senior-engineer nagging, applied without ego.
The pattern: good tools push you toward something. Bad tools push you away from friction and call it comfort.
The audit
Once a season or so, I list the tools I touched most in the last three months and ask one question about each:
What is this tool training me to do?
Some answers have been embarrassing. A social feed training me to want outrage in ninety-second intervals. A to-do app training me to feel busy instead of finished. A language whose ergonomics trained me to avoid entire categories of programs because the tool made them unpleasant.
The point isn’t to quit the tools. It’s to know which arguments you’re losing.