Why I keep coming back to the terminal

Most of the tools I reach for most often are old. Not because I'm nostalgic, but because they've had decades to become exactly what they need to be — nothing more, nothing less.

The terminal is the clearest example of this. It has no loading spinner, no onboarding flow, no dark pattern nudging me toward a premium tier. It just waits. And when I type, it responds.

The constraint is the feature

GUI tools abstract away decisions. That's their value proposition. But abstraction has a cost: you stop understanding what's actually happening. The terminal refuses to abstract. Every command is a small contract — input goes in, output comes out, and the whole thing is auditable.

The best tools are the ones that make you better at thinking, not just faster at clicking.

When something breaks in a GUI, you click around hoping. When something breaks in the terminal, you read the error. One of those habits compounds.

Muscle memory as infrastructure

There's something else too. After enough time, the commands stop being commands. cd, ls, grep, git log --oneline — these become extensions of thought. The friction between idea and execution drops to nearly zero.

That's rare. Most software fights you. The terminal, once learned, gets out of the way entirely.