Certificate

# ===== Skills checklist =====
# After the VS Code track you should be able to:
# [x] Move around without the mouse (Ctrl+P, Ctrl+T, F2, etc.)
# [x] Edit with multi-cursor + structural selection
# [x] Configure format-on-save with the right formatter per language
# [x] Sync settings across machines
# [x] Author + share .vscode/tasks.json for the team
# [x] Use the integrated terminal effectively (profiles, multiple shells)
# [x] Write your own snippets for repeated chores
# [x] Use the Source Control panel + diff editor for staging
# [x] Configure debug launch configs for Node, Python, Go, etc.
# [x] Use Remote-SSH / Dev Containers / Codespaces for isolated environments
# [x] Restrict workspace trust + avoid auto-running untrusted code
# [x] Use task profiles (Frontend, Backend, ML) to scope extensions

# ===== Bookmark =====
# - https://code.visualstudio.com/docs           official docs
# - https://github.com/microsoft/vscode-tips-and-tricks
# - https://marketplace.visualstudio.com         extensions
# - https://www.barbarianmeetscoding.com/blog/vim-for-vs-code-users (Vim mode)

# ===== Portfolio project (4-8 hours) =====
# Publish a 'dotfiles' repo that captures your VS Code setup:
# 1) settings.json with sensible defaults
# 2) keybindings.json with your shortcuts
# 3) snippets/ with language-specific shortcuts
# 4) .vscode/extensions.json (recommended extensions)
# 5) tasks.json for common project scripts (test, lint, build)
# 6) launch.json for the debug configs you use
# 7) shell aliases (code --diff, code --wait)
# 8) README that explains why each setting is set

# Bonus:
# - GitHub Codespaces config (.devcontainer/devcontainer.json)
# - Per-language workspace files for the projects you work on
# - A blog post 'Why I configure VS Code this way'

# ===== What 'good' looks like =====
# - Settings sync ON (your config follows you to any machine)
# - format-on-save: ON; per-language formatters configured
# - Tasks documented; team can run them
# - Snippets for the repetitive boilerplate in your stack
# - Recommended extensions kept short (< 20)

# ===== Common mistakes to avoid =====
# - 50 extensions installed -> editor is slow
# - 'Update settings later' -> never gets done
# - Skipping settings sync -> redo setup on every laptop
# - Not committing .vscode/tasks.json -> teammates do not benefit
# - Fighting the editor instead of learning 5 shortcuts per week

# ===== Next steps =====
# - Vim mode if you want a Vim-VSCode hybrid
# - Live Share for pair programming
# - GitHub Copilot for AI assistance
# - Remote-SSH for working on production hosts
# - Dev Containers for reproducible dev environments

# ===== Self-test =====
# If you can:
# 1) Open any file in your project in <1 second without the mouse
# 2) Run tests with a single keystroke
# 3) Onboard onto a new project in <5 minutes via .vscode + extensions.json
# you have completed the track. Ship the dotfiles and call it done.

# ===== Track wrap-up =====
# VS Code rewards keyboard fluency more than configuration. Spend the
# afternoon on settings sync + 10 keybindings + tasks.json + snippets, and
# the editor stops being the friction in your day. The published dotfiles
# are evidence that you take craft seriously.

// /certificate/vscode