Project Setup, Navigation, and Refactoring

Open a project rather than a single file

Start from the build root: pom.xml or Gradle settings for Java, package.json and tsconfig for TypeScript, go.mod/go.work for Go, and pyproject.toml for Python. Run the existing build or test command before changing editor settings.

Use one repository root when it represents one build graph. Use multi-root workspaces for independently configured services. Avoid including the same source through both a parent and child folder.

Separate personal profiles from shared project settings

Create a profile with Profiles: Create Profile. Keep fonts and keymaps in User/Profile settings; keep formatter ownership and task commands in the repository. A profile export does not lock tool versions. Profiles

Inspect publisher and extension IDs. Record installed versions with code --list-extensions --show-versions. Recommendations do not automatically install or pin extensions. Extension management

For a new learning project, begin with automatic transformations disabled. Enable the appropriate language settings later through the formatting lab.

{
    "files.autoSave": "off",
    "editor.formatOnSave": false,
    "editor.formatOnPaste": false,
    "editor.formatOnType": false,
    "editor.formatOnSaveMode": "file",
    "editor.codeActionsOnSave": {
        "source.fixAll": "never",
        "source.organizeImports": "never"
    },
    "editor.bracketPairColorization.enabled": true,
    "editor.guides.bracketPairs": true,
    "editor.stickyScroll.enabled": true
}

Language overrides can still take precedence. Search Settings using @modified, @lang:go, or @ext:golang.go before diagnosing a provider. Settings scopes

Learn commands by the task they solve

These are common default bindings; verify the active OS and keymap in Keyboard Shortcuts. Linux desktop bindings can intercept function keys.

See the essential shortcuts reference for separate Windows, Linux, and macOS bindings.

In Quick Open, append :42 to jump to a line. Use Outline, Breadcrumbs, implementations, and call hierarchy to understand structure. Search text for configuration keys or log strings; use semantic Rename for functions. Keybindings, navigation

Make refactoring reviewable

Find references to calculateTotal, rename it to calculateSubtotal, inspect the diff, and run focused tests. Search separately for serialized names, SQL, reflection, and string-based dependency injection. Language services cannot promise to update those contracts.

Select an expression or block and inspect Refactor… for extraction actions. Availability depends on language and selection. Use multi-cursors for repeated text, preview regex replacements, and stage only intended hunks. Refactoring, basic editing, Source Control

Twenty-minute exercise and videos

1. Open a small project and run its tests.
2. Navigate from a symbol to its definition, references, and back.
3. Rename an internal function and inspect callers in other files.
4. Extract part of a function, then rerun the same tests.
5. Review the diff for unintended formatting.

Watch Fireship's 25 VS Code Productivity Tips and Speed Hacks: publisher chapters at 02:43, 07:14, and 10:50 cover symbols, Tasks, and Rename. Reproduce those three tasks instead of installing every demonstrated extension. For a broader introduction, use freeCodeCamp.org's Visual Studio Code Crash Course.

The official Profiles video provides a profile workflow. Use current reference material for settings, and measure success by completing the exercise with passing tests.

Shortcuts and extension setup

Use essential shortcuts for OS-specific navigation, editing, and debugging. Choose an installation scope in language extensions and combined Profiles.