Live in the Terminal

The most productive engineers I've worked with share one unglamorous habit: they live in the terminal. Not out of nostalgia, and not to look hardcore. They live there because it's where the loop is tightest.

Every good tool is really a feedback loop, and the best loop ever built for thinking with a computer is the REPL — Read, Evaluate, Print, Loop. You type a line, you see the result, you adjust, and the whole cycle takes a heartbeat. Great programmers don't write a large program and pray; they poke at the problem interactively, one expression at a time, until they understand it, and only then commit it to a file. The REPL turns programming from an essay you submit into a conversation you have.

The command line is the same idea at the level of the whole system. Small tools, each doing one thing, piped together into something none of them could do alone. A command is composable, repeatable, and one edit away from becoming a script that runs a thousand times. There is no ceiling. Whatever you can describe, you can wire together and automate — which is exactly the property a mouse and a menu can never give you.

The industry keeps trying to bury all of this under something friendlier: the IDE, the dashboard, the drag-and-drop console. Those tools are genuinely more welcoming. But every one of them is a layer someone else placed between you and the machine, and that layer decides in advance what you're allowed to want. The GUI shows you the options its designers imagined. The terminal does what you say. Friendliness is a wonderful on-ramp and a terrible ceiling.

Here's the part that surprised people: AI didn't kill the command line. It moved in. The most capable AI coding tools don't live in a chat box; they live in the terminal, reading files, running commands, watching what breaks, and trying again. That's not an accident. An agent needs exactly what the terminal provides — a tight feedback loop and composable actions it can chain without asking permission. The REPL loop and the agent loop are the same loop. The machines learned to work in the place we should have been all along.

So the advice writes itself, and it's the same advice it was twenty years ago, only more urgent. Learn your shell. Build the REPL habit — reach for the interactive prompt before the big file. Prefer tools that compose over tools that trap you in their window. The leverage was always here; now it's the native habitat of your most powerful collaborator too.

The GUI shows you what someone else decided you would need; the terminal does what you tell it. Tighten the loop, and everything else follows. Even the newest cowork tools only chain more windows together inside the GUI — and chaining windows will always be weaker than stripping the UX layer away entirely.