Photo by Pankaj Patel on Unsplash

So I was pair programming with a junior dev last week and watched them manually click through menus to rename a variable — across twelve files. Twelve. I said nothing for about ten seconds because I just couldn't process what I was seeing. Then I gently introduced them to multi-cursor editing and watched their mind visibly break. That moment reminded me how many genuinely useful VS Code tips and tricks just never get discovered because nobody tells you about them.

I've been using VS Code since basically version 1.0, and I still find stuff that makes me go "wait, that was always there?" So let's skip the stuff everyone already knows — yes, I know about Emmet, yes, I know you can split the editor. Here's what actually changes your day-to-day workflow.

The Multi-Cursor Thing (But the Part Nobody Shows You)

Everyone knows Alt+Click adds a cursor. But here's the one that saves me constantly: if you select a word and hit Ctrl+D (Windows/Linux) or Cmd+D (Mac), it selects the next occurrence of that word. Keep hitting it and you keep adding selections. Then you type and edit all of them at once. Super useful for renaming something locally without triggering a full project-wide refactor.

The insider move though? Ctrl+Shift+L selects ALL occurrences in the file instantly. That's the one that drops jaws.

Command Palette Is Your Best Friend (Seriously, Stop Using Menus)

Hit Ctrl+Shift+P (or Cmd+Shift+P on Mac) and just... start typing whatever you want to do. Format document, toggle word wrap, change language mode, install extensions — all of it. I'd say 80% of the time I need a setting or action, I go here first. Way faster than hunting through the UI.

The related shortcut that people skip: Ctrl+P alone opens the quick file switcher. Type part of a filename, jump to it instantly. You can even type : followed by a line number to jump directly there, like filename.js:142. Huge for navigating large projects.

The Settings JSON File Is Where the Real Power Lives

VS Code's GUI settings are fine for basics, but if you want to really configure your environment, you need to get into settings.json. Open the Command Palette, search "Open User Settings JSON" and you're in. This is where I keep things like:

{
  "editor.formatOnSave": true,
  "editor.tabSize": 2,
  "editor.wordWrap": "on",
  "files.autoSave": "afterDelay",
  "files.autoSaveDelay": 1000,
  "editor.minimap.enabled": false
}

Turning off the minimap alone frees up real estate I didn't know I was missing. And formatOnSave with Prettier configured is something I consider non-negotiable on any machine I'm working on. If you're setting up a new machine, just copy your settings.json over — done. No clicking through menus to reconstruct your environment.

Integrated Terminal Tricks Most People Ignore

Open the integrated terminal with Ctrl+` (that's the backtick key). You already knew that. Here's what you might not know: you can split the terminal panel into multiple terminals side by side with Ctrl+Shift+5. I run my dev server in one, git commands in another, and maybe a log watcher in a third — all without leaving VS Code.

Also, right-click the terminal tab area and you can rename each terminal. Sounds minor, I know. But when you've got five of them open and they're all called "bash," you'll wish you'd done this from the start.

Peek Definition vs. Go To Definition — Know the Difference

Most people know F12 for "Go to Definition" — it jumps you to wherever a function or variable is defined. But that's disruptive when you just want a quick look. Use Alt+F12 instead for "Peek Definition." It opens an inline popup right where your cursor is, shows you the definition, and you can close it without losing your place. This one is legitimately underused.

Related: Shift+F12 shows all references to a symbol across your project. That's your "who's actually using this function" command, and it's invaluable before you delete something you think is unused. (I've been burned by skipping this step. More than once.)

The Insider Trick I Don't See Talked About Enough

Here's one that took me embarrassingly long to discover: Zen Mode. Hit Ctrl+K Z (two-key chord — press Ctrl+K, release, then press Z). Your editor goes full screen, hides everything, and you're left with just the code. Perfect for when you need to actually focus instead of being distracted by your file tree, terminal, and the twelve extensions you've accumulated.

Press Escape twice to exit. Clean, simple, and way more useful than I expected when I first tried it.

The other one — and this is the actual insider tip — is Workspace Trust combined with Profiles. VS Code now lets you create separate profiles with different extensions, themes, and settings. So your Python profile doesn't have all your JavaScript tooling loaded, which means faster startup and less noise. Go to File > Preferences > Profiles to set them up. If you work across multiple stacks, this is a game changer.

One Quick Productivity Setting to Change Right Now

Go into your settings.json and add this:

"editor.linkedEditing": true

For HTML and JSX files, this means when you rename an opening tag, the closing tag updates automatically. No more finding out you broke your markup because the tags got out of sync. It's one of those tiny things that saves you maybe thirty seconds a week individually, but adds up to a lot less frustration over time.

Anyway, VS Code is one of those tools where there's always something new to find — and honestly, the official VS Code tips productivity docs are actually decent for going deeper once you've got the basics locked in. Hope this saves you some time, or at the very least, saves someone nearby from watching you click through menus ever again.