The Slack story is wrong. Most developers do not lose deep work to Slack. They lose it inside their editor, to small frictions that never look like a problem in the moment.
A 12-second hunt for a file. A terminal split that takes three clicks. A notification banner that breaks a thought. None of them are a crisis. All of them, stacked across a day, are the difference between shipping and grinding.
This is the VS Code setup we run, and the audit we use to find what is still leaking.
Start with the principle, not the settings
Before any config, decide what your editor is for. There are two honest answers:
- A typing surface. You write code, you read code, you ship.
- A dashboard. You watch CI, chat, terminals, file trees, and panels.
If your editor is a typing surface, ruthlessly hide everything that is not text. If it is a dashboard, accept the cost. There is no middle setting that works.
Most of this post assumes option one.
The deep work configuration
These are the settings that buy back the most attention. Drop them into your settings.json and read each one before you save.
{
"editor.minimap.enabled": false,
"editor.scrollbar.vertical": "hidden",
"editor.scrollbar.horizontal": "hidden",
"editor.lineNumbers": "on",
"editor.renderWhitespace": "boundary",
"editor.cursorSmoothCaretAnimation": "on",
"workbench.activityBar.location": "hidden",
"workbench.statusBar.visible": true,
"workbench.editor.showTabs": "single",
"breadcrumbs.enabled": true,
"files.autoSave": "onFocusChange",
"git.autofetch": true,
"notifications.showExtensionsWithUpdatesAvailable": false
}
A few notes:
- Minimap off. It looks useful, it is mostly noise. Use
Cmd/Ctrl + Pto navigate. - Activity bar hidden. You can reach every panel with a shortcut. Keep the screen quiet.
- Single tab mode. Forces you to use quick open. Painful for two days, then permanent.
- Auto-save on focus change. Removes a class of mistakes (stale builds, wrong file, lost work) without the noise of save-on-keystroke.
The five shortcuts that change everything
If you only ever learn five VS Code shortcuts, learn these. Memorize them in this order.
| Shortcut | What it does | Why it matters |
|---|---|---|
Cmd/Ctrl + P | Quick open any file | Replaces tree navigation |
Cmd/Ctrl + Shift + P | Command palette | Replaces 80 percent of menu use |
Cmd/Ctrl + B | Toggle side bar | Reclaim screen for typing |
Cmd/Ctrl + (backtick) | Toggle terminal | Stop alt-tabbing to a separate app |
F2 | Rename symbol | Safe project-wide rename |
If any one of those is unfamiliar, that is your first audit finding.
The terminal lives in the editor, or it does not
Pick one. Either your terminal lives inside VS Code (Cmd/Ctrl + `) and you commit to it, or it lives in a dedicated app like iTerm or WezTerm and you alt-tab.
What does not work is half-and-half. Half-and-half means you keep losing track of which terminal has which process, and you spend 20 seconds a switch trying to remember.
Our recommendation: integrated terminal for anything tied to the project (dev server, tests, git). Dedicated terminal for everything else (ssh, system stuff, scratch).
The audit that finds what your config cannot
Settings and shortcuts only help with patterns you already know about. The expensive losses are the ones you cannot see from the inside.
Run this:
- Record 30 minutes of normal coding. Use the OS screen recorder, or any tool that captures activity.
- Watch it back at 2x speed.
- Pause every time you do one of the following: hesitated more than 2 seconds, used the mouse for something a shortcut would have done, switched windows, or ran the same command twice.
- Write down the timestamp and the action.
After 30 minutes of footage, you will have a list of 8 to 15 specific frictions. Most are 2-line fixes (a keybinding, a setting, a snippet). The total time recovered is usually 30 to 60 minutes of deep work per day.
This is exactly the audit Upskill automates. Upskill watches a recording of your real work session and returns timestamped insights: time-wasting patterns, workflow inefficiencies, automation opportunities, and specific improvements. For developers, that means the editor habits, the terminal patterns, and the deploy rituals you cannot see from inside the work.
A weekly rhythm that keeps the setup honest
Configurations rot. Extensions stack up. Shortcuts get forgotten. Once a quarter, run this checklist:
- Open the extensions list. Disable anything you have not consciously used in 30 days.
- Open
keybindings.json. Anything you defined six months ago and never use, delete. - Run a 15-minute recorded audit. Find the new bottleneck.
- Adjust one setting, one shortcut, one habit. Just one.
Small, regular adjustments outperform a once-a-year setup overhaul.
What to do this week
Pick one of the five shortcuts above that you do not use yet. Force yourself to use it for the next three days, even when it is slower. By day four, it will be faster than your current habit, and your hands will have one less reason to leave the home row.
For more developer-focused playbooks, including git rituals and PR review patterns, browse the Developers cluster.
Frequently asked questions
What is the single most important VS Code shortcut to learn?
Cmd/Ctrl + P. Quick file open. If you are still using the file tree to navigate, you are paying a 5 to 10 second tax every time you switch files. Internalizing quick open recovers more time than any other single shortcut.
Are AI extensions like Copilot worth the context switch cost?
Yes for boilerplate, no for architecture. Copilot is a strong autocomplete and a weak architect. Use it for tests, types, and repetitive transforms. Turn it off, or scope it to specific files, when you are designing a system.
How do I stop notifications from breaking flow?
Disable VS Code notifications in settings, mute Slack and email for the duration of a focus block, and put your phone in another room. Most developers underestimate how much each ping costs: studies suggest 15 to 25 minutes to fully recover focus.
Should I use a tiling window manager or just VS Code's built-in panels?
Built-in panels are enough for 90 percent of developers. Split editor, terminal panel, and the side bar cover most layouts. A tiling WM helps if you regularly run a browser, terminal, and editor side by side, and you switch between them by keyboard.
How do I find my own time-wasting patterns inside the editor?
Record a 30-minute coding session and watch it back. Or use a tool like Upskill that watches the recording for you and tags the moments where you hesitated, repeated, or backtracked. The patterns are almost always invisible from the inside.