the editor as a force multiplier

most engineers spend eight hours a day in their editor. small inefficiencies in it compound into days per year. that’s the pitch for spending an afternoon on configuration. the underlying argument is the same as john ousterhout’s a philosophy of software design: the parts of your environment you touch most often deserve the most thought. the editor is the most-touched tool an engineer owns.

wins kept

the half-hour wins i’ve made and never undone:

• fuzzy file open, bound to one chord. cmd-p in vscode, ctrl-p, telescope in neovim. typing two-thirds of a filename and pressing enter is faster than any tree.
• multi-cursor, real ones. select-all-occurrences. column edit. the shape of an edit determines the cursor pattern; if you can describe the edit in words (“change every Foo in this file to Bar”), there’s a cursor pattern that does it.
• snippets for boilerplate. a typescript test scaffold should be a four-character expansion. the time you save typing curly braces isn’t the point — the point is staying in the loop without breaking flow.
• lsp + go-to-definition. clicking through stack traces by hand is the dev equivalent of using a knife handle to drive a screw.
• multi-line yanking and registers. pasting in a different shape than you copied is a daily move. learning your editor’s clipboard model pays back monthly.

wins undone

the half-hour wins i’ve made and did undo:

• elaborate file trees on the left. they look organised. they cost a click to use. fuzzy open is faster.
• twenty-color themes. high-contrast monochrome turns out to scan faster after about a week.
• vim-mode in editors that aren’t vim. the impedance is real. either go all-in or don’t.

ai-augmentation now sits on top of all this. cursor, claude code, copilot — they make slow editors slower, because the suggestion window has to compete with file-tree mouse-clicks. the more fluent your editor flow, the more the model amplifies it. the less fluent, the more it gets in the way.

an afternoon of editor config is not procrastination. it’s the same logic as sharpening a saw.