When I switched from a mouse to a trackpad, I stopped using Photoshop and started using Figma. Not because Figma is better — because the gestures are different. A mouse is precise. A trackpad is fluid. Precise tools make you think in points and pixels. Fluid tools make you think in flows and relationships.
I didn't decide to think differently. The tool decided for me.
The Sapir-Whorf Hypothesis for Tools
Linguists have this idea — the Sapir-Whorf hypothesis — that the language you speak shapes the thoughts you can think. If your language has no future tense, you think about time differently. If your language has fifteen words for snow, you perceive snow differently.
The strong version of this is probably wrong. But the weak version — that language influences thought without fully determining it — is almost certainly true. And it applies to tools even more directly than it applies to language.
Consider:
| Tool | What it makes easy | What it makes hard |
|---|---|---|
| Spreadsheet | Tabular thinking, formulas | Narrative, ambiguity |
| Whiteboard | Spatial thinking, connections | Precision, version control |
| Text editor | Linear thinking, prose | Visual relationships |
| Slide deck | Sequential arguments | Nuance, depth |
| Terminal | Composable operations | Discovery, exploration |
Each tool creates a path of least resistance, and we follow that path because resistance is expensive. You can write a novel in a spreadsheet. You just won't.
The IDE Effect
This is especially visible in programming. The IDE you use shapes the code you write.
// If your IDE has great autocomplete, you write code like this:
const result = array
.filter(item => item.status === 'active')
.map(item => transformItem(item))
.reduce((acc, item) => mergeResults(acc, item), initialValue);
// If you're in a basic text editor, you write code like this:
const result = [];
for (const item of array) {
if (item.status === 'active') {
result.push(transformItem(item));
}
}Neither is objectively better. But the first style is easier with autocomplete because the IDE suggests the next method in the chain. The second style is easier without it because you can see the full structure at once.
The code you write isn't just a reflection of your skill. It's a reflection of your environment.
The Notebook vs. The App
I keep a physical notebook for certain kinds of thinking. Not because I'm a Luddite — because paper has properties that screens don't.
Paper is:
- Finite. A page has edges. You can't scroll. This forces compression.
- Permanent. You can't undo. This forces commitment.
- Slow. You can't type at 80 WPM. This forces selection.
- Spatial. You can write anywhere on the page. This allows non-linear thinking.
Screens are:
- Infinite. You can always add more. This encourages sprawl.
- Reversible. You can undo everything. This reduces stakes.
- Fast. You can capture everything. This reduces filtering.
- Linear. Most apps scroll vertically. This enforces sequence.
When I need to make a decision, I use paper. When I need to explore possibilities, I use a screen. Not because I've rationally analyzed the affordances — because I've noticed what works.
The AI Shift
This is why AI coding tools matter more than people think. It's not about productivity. It's about what becomes thinkable.
Before AI, if you had an idea that required writing 200 lines of boilerplate, you'd probably think "that's not worth it" and move on. The idea dies in the gap between conception and execution. With AI, that gap shrinks. Ideas that were too expensive to try become cheap to try. The threshold for "worth exploring" drops.
This doesn't just mean you write more code. It means you think more ambitiously. The tool expands the space of thoughts worth having.
The Danger
The danger is invisible. If your tools shape your thoughts, and you're not aware of it, then your thoughts aren't really yours. They're the path of least resistance in whatever tool you happen to be using.
The person who only has a hammer doesn't just treat everything as a nail. They stop seeing things that aren't nails. The screws, the bolts, the things that need glue — they fade from perception.
The antidote isn't to use every tool. It's to notice the walls. To occasionally ask: "What am I not thinking because my tool doesn't make it easy?"
Then switch tools. Even briefly. The thoughts that emerge in the gap between tools — those are the interesting ones.