you NEED to use VS Code RIGHT NOW!!

TL;DR

Install VS Code from code.visualstudio.com and start by opening a folder as a project workspace.

Briefing Cornell Notes

Briefing

VS Code is positioned as an all-in-one workspace for writing code, running it, and managing remote systems—so much so that it can be used locally, in the browser, or directly inside cloud and SSH sessions. The practical message is simple: install VS Code and start using its core workflow immediately, then expand into extensions for Python, remote development, Docker, and major cloud platforms.

The walkthrough starts with how ubiquitous VS Code has become. A GitHub repository can trigger VS Code “mode” via a keyboard shortcut, and VS Code can also run in the browser. Still, the recommended path is local installation from code.visualstudio.com, followed by opening a folder as a project. From there, creating a new file brings up VS Code’s command palette and editor features, with syntax highlighting that automatically recognizes Python and color-codes functions, strings, parentheses context, and related structures.

Next comes the “quality of life” layer that makes the editor feel interactive. Installing the Python extension from Microsoft enables linting (squiggly-line warnings when code is off, such as typing prints instead of print) and IntelliSense, which offers suggestions and auto-completion as code is typed. The result is faster iteration: the editor flags likely mistakes and proposes the next tokens, including completing loops and other constructs with tab-based selection.

Running code inside VS Code is treated as equally important. A play button launches execution, and on Windows—where Python may not be installed by default—VS Code prompts for a Python interpreter and can install Python from the Windows Store. Once configured, the run produces output and opens an integrated terminal. The terminal supports typical shell workflows (PowerShell on Windows), and VS Code can split terminals to run multiple commands side by side.

From there, the workflow expands beyond the local machine using cloud and remote development. A cloud VS Code server can be created through Linode by installing a VS Code marketplace image on a low-cost plan, then connecting via reverse DNS. But the deeper “pro” feature is Remote SSH via the Remote SSH extension: it lets VS Code open folders on a remote Linux host over SSH, automatically setting up a VS Code environment there. In the remote session, the editor shows the remote filesystem (for example, opening the remote “root” folder), and terminal commands run on the remote host.

Because extensions are environment-specific, Python support may need to be installed again on the SSH host. The same pattern applies to richer tooling. VS Code can preview images and play videos directly in the editor even when connected to a server without a graphical desktop. With the Microsoft Docker extension installed on the remote host, VS Code lists running containers, shows images, inspects container filesystems, and supports attaching to a container shell. It can also open web pages for services when ports are available, and provides views for networks and volumes.

Finally, cloud management is brought into the editor through Azure and AWS extensions, enabling resource creation and browsing without leaving VS Code. The overall takeaway is that VS Code becomes the control center: code locally, run it instantly, and then extend the same interface to remote servers, containers, and cloud resources through extensions.

Cornell Notes

VS Code is presented as a unified coding and operations workspace that works locally, in the browser, and on remote machines. After installing VS Code and opening a folder as a project, the Python extension adds linting and IntelliSense, making code faster to write and harder to break. Running code uses the built-in play button and integrated terminal; on Windows, VS Code can prompt for and install a Python interpreter. The Remote SSH extension then shifts the entire editor experience into a Linux host over SSH, where extensions may need to be installed again for that environment. With additional extensions—Docker, Azure, and AWS—VS Code can manage containers and cloud resources directly from the same interface.

What are the first “must-use” steps after installing VS Code?

Open VS Code, then use File → Open Folder to treat a folder as the project workspace. Create a new file via File → New File and name it (for example, a Python file). VS Code will often detect the language automatically (Python syntax highlighting appears immediately).

How do linting and IntelliSense change day-to-day Python editing?

After installing the Python extension from Microsoft, VS Code flags likely mistakes with squiggly-line linting (e.g., typing prints instead of print). IntelliSense provides context-aware suggestions and auto-completion as code is typed, including completing common structures like loops; tab can accept the most specific completion.

How does VS Code run code and handle missing dependencies on Windows?

A play button in the editor runs the current script and shows output while also opening an integrated terminal. If Python isn’t installed on Windows, VS Code prompts for a Python interpreter and can install Python from the Windows Store, after which the interpreter selection enables successful runs.

What does Remote SSH add beyond local editing?

Remote SSH (installed from the Extensions tab) lets VS Code open folders on a remote machine over SSH. After connecting, the bottom-left indicator shows an SSH session, and File → Open Folder can target the remote filesystem (such as opening /root). Terminal commands run on the remote host, and the editor environment may require installing extensions like Python on the remote side.

How far can VS Code go with Docker and cloud tooling?

With the official Microsoft Docker extension installed on the remote host, VS Code can list running containers, inspect container filesystems, stop/restart containers, and attach to a container shell. It can also open services in a browser when ports are available. For cloud resources, Azure and AWS extensions allow creating and browsing resources from within VS Code, including signing into Azure via a web login flow.

Review Questions

When would you need to install the Python extension twice—once locally and once on a remote host?
What specific VS Code features help catch Python mistakes while typing (not after running)?
How does Remote SSH change where the terminal commands execute compared with local VS Code?

Key Points

1
Install VS Code from code.visualstudio.com and start by opening a folder as a project workspace.
2
Use the Python extension from Microsoft to enable linting (squiggles) and IntelliSense auto-completion.
3
Run scripts with the play button and rely on the integrated terminal; on Windows, VS Code can prompt to install a Python interpreter.
4
Use Remote SSH to edit and operate on a Linux server over SSH while keeping the same VS Code interface.
5
Install extensions inside the remote environment when needed (e.g., Python) because capabilities don’t automatically carry over.
6
Add the Microsoft Docker extension to manage containers—inspect filesystems, attach shells, and view networks/volumes.
7
Use Azure and AWS extensions to create and manage cloud resources without leaving VS Code.

Highlights

VS Code’s Python extension turns typing into an assisted workflow: linting flags errors immediately, while IntelliSense suggests and completes code as it’s written.

Remote SSH makes VS Code behave like a remote control for Linux: folders open on the server, terminals run remotely, and the editor environment is tied to the SSH host.

With the Microsoft Docker extension, VS Code can inspect containers and attach to their shells, and it can open exposed services in a browser when ports are available.

Azure and AWS extensions bring cloud resource management into the same command palette and interface, including sign-in flows for Azure.

Topics

VS Code Setup
Python Extension
Remote SSH
Docker Integration
Cloud Extensions