Vim Motions Actually Work (And Why You Should Try Them)

I use Neovim. There, I said it. Before you click away thinking "oh great, another Vim user telling me my IDE is garbage" — sit down, shut up, and hear me out. I promise I won't say hjkl more than... okay, I'll say it a few times. But there's a reason.

Why Vim Motions Are Actually Insane

Here's the thing nobody tells you when you're starting out as a developer: you spend roughly 90% of your time reading code and moving around files, not actually typing new code. The bottleneck isn't your typing speed. It's how fast you can navigate, select, delete, rearrange, and manipulate the text that's already there.

Vim motions are like giving your keyboard a PhD in text manipulation. ciw — change inner word. da{ — delete around braces. yap — yank a paragraph. You're not pressing keys one at a time anymore; you're composing commands. It's like going from pointing at letters on a whiteboard to writing actual sentences.

Does it feel weird at first? Absolutely. You will open Vim, try to type, and nothing will happen. You will Google "how to exit Vim" at 2 AM and question every life decision that led you here. That's normal. That's the initiation ritual. After about a week, something clicks, and suddenly your mouse feels like a steering wheel made of wet spaghetti.

But It's Not for Everyone (And That's Fine)

Look, I'm not going to pretend Vim motions are the answer to all your problems. If you're happy in VS Code, if your workflow is smooth, if you're shipping code and solving problems — you don't need Vim. Vim motions won't fix your broken TypeScript types. They won't debug your React re-renders. They won't make your Python script run faster.

But if you've ever felt like your editor is slowing you down — if you find yourself reaching for the mouse every 3 seconds, if you're tired of clicking through menus, if you want to feel like you're actually controlling your code instead of just editing it — then Vim motions might be worth a look.

The best part? You don't even need to use Neovim to try them.

The "Try Before You Commit" Starter Pack

Before going full Neovim, try Vim motions in your current editor:

• VS Code — Install the vscodevim extension. That's it. You get Vim keybindings inside VS Code. Keep your extensions, keep your theme, keep your comfort. Just start moving faster.
• Zed — Has built-in Vim mode. Toggle it on, and you're good. Zed is fast as hell too, so you get Vim motions and a modern editor.
• JetBrains — The IdeaVim plugin. Same deal. Vim inside your existing IDE.

If after a month you're thinking "okay, this is actually kind of nice" — then maybe it's time for Neovim. And if you want a starting point that won't make you want to throw your laptop into the sea, use kickstart.nvim.

Kickstart is a single-file Neovim config maintained by TJ DeVries (the guy who basically built half of the Neovim ecosystem). It's not a distribution — it's a starting point. One file. You read it, you understand it, you customise it. No 400 plugins you'll never configure. No black magic. Just Lua code you can actually read.

Next up: Part 2 — My Neovim Config (and How It Actually Works) — a full walkthrough of my modular config, every plugin and why it's there, the hand-built statusline, and the sensible defaults that make the whole thing tick.

If you want a starting point, my config is on GitHub. Kickstart.nvim is where it all began — and this video is the best walkthrough I've found for getting started from scratch.