The cursor blinked, but my hands didn’t move. Not because I didn’t know what to type — but because the path between thought and action was clogged with tiny, pointless steps.
This is the hidden tax on creative work: friction. Every time you pause to remember a shortcut, hunt for a file, or switch tools, you pay in seconds and focus. In programming, those seconds stack into hours, and the mental cost is even steeper. The question is simple: how do you cut these delays until they disappear?
Emacs is a tool built for this fight. It’s been shaped for decades by people obsessed with speed, flow, and directness. But too many use it like any other editor, unaware of how it can be tuned until it feels like a direct extension of their thoughts. Reducing friction in Emacs isn’t about learning every command. It’s about shaping the environment so the work stays unbroken.
Start with the basics: keep your hands on the keyboard. Remap keys you use often so they’re within easy reach. Remove commands you never use so they don’t crowd your muscle memory. Build small, composable functions that match the way you think. Let your environment guide you, not interrupt you.