VS Code is the student control room.

Why VS Code matters

VS Code is one of the best tools for students because it works across many kinds of projects: Python scripts, Java assignments, C++ labs, static websites, Flask apps, Markdown notes, GitHub repos, and remote Linux servers.

Install VS Code

VS Code is free and runs on Windows, macOS, and Linux. On Linux, I usually install it from the official package. On Debian or Ubuntu-based systems, the downloaded .deb package can be installed with apt.

# After downloading the official .deb package
sudo apt install ./code_*.deb

Want to try it before installing?

VS Code itself is free, but I do not even need to install it first to understand the workflow. GitHub Codespaces gives me a VS Code-style editor in the browser with a Linux terminal attached to a GitHub repo.

Open a project the right way

The best habit is to open the whole project folder, not just one file. That lets VS Code understand the folder structure, Git repo, terminal location, and project settings.

# Go to a project folder
cd ~/projects/launchshell-org

# Open the folder in VS Code
code .

My normal VS Code workflow

This is the loop I use for most student projects.

The integrated terminal is the key feature

The terminal inside VS Code is not a fake terminal. It runs my normal shell inside the project folder. That means I can use the same Linux commands I would use in a separate terminal window.

Ctrl + `

pwd
ls

python3 weather.py --zip 11234
javac Movies.java
python3 -m http.server 8000

git status --short
git diff
git add .
git commit -m "Add VS Code guide"

Install useful extensions

Extensions are what turn VS Code into a good editor for specific languages and workflows. I do not need hundreds of them. I need the right few.

Use the command palette

The command palette is one of the fastest ways to control VS Code. Instead of searching through menus, I can type what I want to do.

Ctrl + Shift + P

Preferences: Open Settings

Preferences: Open Keyboard Shortcuts

Extensions: Install Extensions

Remote-SSH: Connect to Host...

Use VS Code with Git

VS Code makes Git easier because I can see changed files, inspect diffs, stage changes, and commit. I still like knowing the terminal commands because they are portable.

git status --short
git diff
git add index.html assets/site.css
git commit -m "Add VS Code guide"
git push

Use VS Code for LaunchShell HTML work

For a static HTML/CSS site like LaunchShell, VS Code is a clean setup because I can edit HTML, check CSS, serve the folder locally, and commit the changes from one workspace.

# From the LaunchShell project root
python3 -m http.server 8000

http://localhost:8000/

guides/vs-code/index.html

assets/site.css

python3 -m http.server 8000

git diff --check
git status --short

Use VS Code for Python scripts

Python projects are a good fit for VS Code because I can edit the script, run it in the terminal, and use Git from the same workspace.

# Example: Tiny Terminal Weather project
cd ~/projects/tiny-terminal-weather
code .

python3 weather.py --zip 11234

Use VS Code for Java assignments

VS Code can work for Java class projects, especially small single-file assignments or data structures projects. I still want to know the raw compile and run commands.

# Compile and run a Java file
javac Movies.java
java Movies

# Another example
javac RadixIP.java
java RadixIP

Use VS Code for C++ labs

For C++ assignments, VS Code is useful, but the compiler still matters. On Linux, I usually want g++ and sometimes gdb for debugging.

sudo apt update
sudo apt install build-essential gdb -y

g++ main.cpp -o main
./main

Remote SSH is one of VS Code's superpowers

Remote SSH lets me connect VS Code to a remote machine and open a folder there. This is useful for VPS work, Raspberry Pi projects, Linux servers, and cloud labs.

# Example SSH config entry
Host launchshell-vps
    HostName example.server.ip
    User deploy
    Port 4222
    IdentityFile ~/.ssh/id_ed25519

Recommended beginner settings

VS Code has many settings. These are a few practical ones that make student work cleaner.

{
  "editor.wordWrap": "on",
  "editor.tabSize": 2,
  "files.trimTrailingWhitespace": true,
  "files.insertFinalNewline": true,
  "terminal.integrated.defaultProfile.linux": "bash",
  "explorer.confirmDelete": true
}

Workspace files worth knowing

VS Code and Git projects often create small config files. Some should be committed. Some should stay local.

Good keyboard shortcuts

I do not need to memorize every shortcut. These are enough to make VS Code faster.

Beginner mistakes to avoid

VS Code is helpful, but it can hide what is happening if I rely on buttons without understanding the project.

My VS Code starter checklist

This is the short checklist I would give a student setting up VS Code for real technical work.

# 1. Install VS Code

# 2. Open a real project folder
cd ~/projects/my-project
code .

# 3. Open the terminal
Ctrl + `

# 4. Confirm project location
pwd
ls

# 5. Run the project manually
python3 script.py
javac Main.java && java Main
g++ main.cpp -o main && ./main
python3 -m http.server 8000

# 6. Check Git before publishing
git status --short
git diff --check

# 7. Ignore private files
echo ".env" >> .gitignore
echo "weather_settings.json" >> .gitignore

Related LaunchShell guides and projects

VS Code is the workspace I would use for many of the projects on this site.

Official docs worth bookmarking

VS Code and Codespaces both have useful official documentation. These are the areas I would start with.

Final idea