Photo by Glen Carrie on Unsplash

So I was pairing with a junior dev last month and watched him manually rename the same variable in like nine different places across a file. One by one. With his mouse. I had to physically stop myself from grabbing the keyboard. That's when I realized — a lot of people are using VS Code like it's Notepad with syntax highlighting, and that genuinely hurts to watch.

I've been using VS Code as my daily driver for years now, and there are a handful of things I use constantly that most people just... don't know about. Some of these I stumbled on by accident, some I got from colleagues, and a few I only found because I was too stubborn to leave my editor when something annoyed me enough. Here's the stuff that actually matters.

Multi-Cursor Editing Is the One You're Missing Most

Back to that variable renaming situation. If you need to edit multiple occurrences of the same word simultaneously, put your cursor on the word and hit:

Ctrl+D (Windows/Linux)
Cmd+D (Mac)

Each press selects the next occurrence and adds a cursor to it. You can then type and all instances change at once. If you want to grab all occurrences in the file immediately, use Ctrl+Shift+L (or Cmd+Shift+L on Mac). This alone is worth the five seconds it takes to memorize.

And if you just want to drop cursors arbitrarily in different spots? Hold Alt (or Option on Mac) and click wherever you want. Weirdly satisfying once you get the hang of it.

The Command Palette Is Your Best Friend and You're Ignoring It

Ctrl+Shift+P (or Cmd+Shift+P) opens the Command Palette. Honestly, if I had to pick one VS Code shortcut to keep, it's this one. Anything you can do in VS Code — change color theme, toggle word wrap, run a task, install extensions, format your document — you can find it here without touching the menu bar.

Here's an insider trick though: if you just want to jump to a file, drop the > prefix and type the filename directly. So Ctrl+P gives you quick file open. And if you want to jump to a specific line in the current file, use Ctrl+G. I use that one constantly when a stack trace gives me a line number.

Settings Sync — Set It Up Once and Never Cry Again When You Switch Machines

I cannot count how many times I've set up a new dev machine and spent an hour trying to remember which extensions I had, what my tab size was, whether I had format-on-save enabled. Settings Sync fixes all of that.

Go to: File > Preferences > Settings Sync > Turn On (or search "Settings Sync" in the Command Palette). Sign in with GitHub or a Microsoft account and it backs up your extensions, keybindings, snippets, and settings. Next machine, sign in, done. Should've been on by default years ago, honestly.

Terminal Tricks Nobody Tells You About

The integrated terminal is great, but the default setup could be better. A few things worth knowing:

You can open a new terminal instance with Ctrl+Shift+` and split the current terminal panel with Ctrl+Shift+5. Super useful when you're running a dev server in one pane and need to run commands in another without losing your scrollback.

Also — and this one blew my mind when I found it — you can click on file paths and error links in the terminal output while holding Ctrl (or Cmd) and it'll open that file directly in the editor. Stack trace says src/utils/auth.js:42? Cmd-click it. Done.

Breadcrumbs + Go to Definition = Actually Understanding Code Fast

If you're working in an unfamiliar codebase — and we all do, constantly — turn on Breadcrumbs. It's the navigation trail that shows your current file location and the symbol you're inside (function, class, whatever). Enable it at:

View > Show Breadcrumbs

Or just search "breadcrumbs" in settings and flip it on. Combine that with F12 for Go to Definition and Alt+F12 (or Option+F12) for Peek Definition — which shows the definition inline without jumping away — and you can navigate a complex codebase without losing your place every five minutes. I use Peek constantly when I just want a quick look at a function signature without opening another file.

The Insider One: Workspace-Specific Settings

This is something I see even experienced devs overlook. VS Code has two levels of settings — User (global) and Workspace (project-specific). If you open your .vscode/settings.json in a project, you can set things that only apply to that repo. Super useful for things like:

{
  "editor.tabSize": 2,
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode"
}

That way your Python project can have 4-space tabs while your JavaScript project uses 2, without you manually switching every time. Commit that .vscode/settings.json to the repo and your whole team gets consistent behavior automatically. No more "why does your code look different than mine" conversations.

One More: Zen Mode When You Really Need to Focus

Okay this one's a little bit of a tangent, but hear me out. When I need to actually concentrate — like writing a tricky algorithm or reviewing something critical — I hit Ctrl+K Z (or Cmd+K Z). That's Zen Mode. Hides everything. Tabs, sidebar, status bar, all of it. Just you and the code. Hit Escape twice to get back to normal. It sounds gimmicky but I've found it genuinely helpful when Slack is open and my brain won't stop context-switching.

Alright, that's the stuff I actually use on a daily basis — not a list of every VS Code feature that exists, just the ones that make a real dent in how fast and sane you work. If I had to pick just one to start with, it's the Command Palette. Learn that, and everything else gets easier to find on your own. Hope this saves you some time.