VS Code
Stop coding like it’s notepad with extra steps.
▶ the lesson · narrated sketch video · tap for sound
the intro
VS Code is the default editor of modern development, and most of its power is one keyboard shortcut away: jumping to any file, searching across the project, running tasks, debugging inline. Learn the ten shortcuts and settings that matter and everything gets faster.
fun fact ✦
VS Code is built on Electron — technically, it is a website that ate the desktop.
the docs
the deep dive
the ideas behind the video — concepts, diagrams, a walkthrough and the traps to avoid
VS Code is not one giant program — it is a small, fast shell with an ecosystem bolted onto it. The download is a chassis; extensions turn it into a Python shop, a Go shop, or a front-end studio. That is why the skill ceiling is not menu knowledge: it is keeping your hands on the keyboard and telling the machine where to jump.
a small shell, a huge ecosystem
key terms
Command Palette
One searchable menu holding every command the editor has. If you forget where a setting lives, this finds it.
Ctrl+Shift+Pworkspace settings
Per-project overrides stored in a .vscode folder. They travel with the repo, so the whole team gets the same editor behavior.
.vscode/settings.jsonformat on save
The editor rewrites style the instant you save, so formatting debates never reach code review again.
"editor.formatOnSave": trueextension
A plugin that teaches the shell a new trick: languages, linters, themes, debugger support.
Prettier, ESLint, GitLenshow it works
- 1Learn the big three
Ctrl+P jumps to any file by typing part of its name, Ctrl+Shift+F searches every file in the project, Ctrl+Shift+P runs any command. Ninety percent of daily speed lives here.
- 2Turn on format on save
Install Prettier, set it as the default formatter, and let saves do the formatting. Style debates end at the keyboard.
- 3Add only the starter five
Prettier, ESLint, Error Lens, GitLens, and a language pack for your stack. Every extra extension costs startup time.
- 4Commit your settings
Keep a .vscode/settings.json in the repo plus an extensions.json with recommendations. New teammates get the good setup on day one.
the code, explained
a settings.json worth committing
side by side
keyboard first
- Ctrl+P jumps to any file
- edits chain without letting go
- works the same on any machine
- scales to huge projects
mouse first
- fine for occasional edits
- menus hide the power features
- slow when touching many files
- hands leave the home row
Two formatter extensions installed means saves can fight each other — code reformats differently every cycle. Pick one default formatter explicitly, and if startup crawls after years of installs, run the built-in Extension Bisect to find the culprit.
quick answers
VS Code or a full IDE like WebStorm?
VS Code wins on weight, price, and ecosystem; heavy IDEs win on deep refactoring and framework magic. Most teams run VS Code and do not miss the rest.
Do I really need extensions?
Out of the box it edits text. Five extensions make it a development environment — that starter pack is the whole cost of entry.
How do I share setup with my team?
Commit .vscode/settings.json and .vscode/extensions.json. Settings sync is for your own machines; the repo is for the team.
quick hits about VS Code
short answers · interviews, tips, trivia & hidden gems