As a designer on VS Code, I get to see how differently developers use the tool every day. Some work almost entirely from the keyboard. Others stack seven panels across an ultrawide monitor. Themes, extensions, shortcuts, and layouts reflect different projects and ways of working.
That fluency comes from both sides. Developers shape VS Code around their work. VS Code, in turn, helps them build faster. This balance matters even more as we build for agent-first workflows. The work may change, but the sense of control built over years should remain—so developers continue to love working in VS Code.
Developers shape the tool
VS Code starts lightweight, then grows with the developer. Developers can safely explore themes, formatting, layouts, and extensions because every choice can be undone. Settings Sync then carries those choices between machines.
But more options do not automatically create more control. Each one adds complexity to the UI and settings list, plus a long-term support cost. The right option earns that cost by removing repeated friction or keeping unnecessary complexity out of the way. Once set, the tool should feel simpler—not merely more configurable.
That tradeoff matters because an option can become an escape route when the team has not made a clear product decision. Customization works when it is easy to find, undo, and carry to another machine. The goal is not more options. It is a workspace that keeps the right things close at hand.
Let efficiencies compound
A shortcut saves seconds once. Repeated use turns it into muscle memory. The same is true of Tasks, the Command Palette, multi-cursor editing, and other small efficiencies built into VS Code. Each discovery rewards learning by removing a little friction. Together, they change how the editor feels.
It's the same pattern as learning to type. At first, you spend time finding each letter key. Then you practice enough to build rhythm and muscle memory. That investment in learning pays off immediately: you save time and feel more fluent. As you get faster, you stop thinking about the movement itself and start focusing on the words you want to write. Eventually, typing disappears into the background, leaving only the thought you want to express.
- Reward
- Repetition
- Speed
- Comfort
Consistency gives learning a foundation, but it does not mean standing still. We learn by watching how developers work and by using the tool ourselves every day, then simplify the paths they use most. Each change should make an efficiency easier to discover, a choice easier to understand, or a preference easier to carry forward. That helps more developers build the fluency that makes the tool feel comfortable. Comfort is the confidence to stay focused without stopping to think about the tool itself.
Moving forward
We've learned to balance making VS Code a great place to learn how to code with making it a tool professional developers love—without asking anyone to learn everything at once. Great tools are personal, learnable, and rewarding over time. How can we carry this forward, and what can other tools learn from it?
- Aim for comfort as the ultimate goal of a well-loved tool. Define what comfort means for your tool, then relate ongoing feedback to that goal.
- Fight for the lightweight experience. Define a strict bar and clear principles for what “lightweight” means, then stand by them. Reveal customization later, through exploration and in relevant moments.
- Options should make the tool feel simpler. Make sure each option unlocks a real, measurable efficiency worth learning—and never becomes an escape route for a difficult UX decision.