You’ve picked a code editor and maybe installed Python. Now it’s time to put the pieces together into a working coding environment — the actual setup you’ll use every time you sit down to write code.
If you’ve read our guides on code editors and installing Python, you already have the two biggest pieces of a coding environment in place. This guide connects those pieces together and adds the handful of remaining habits — like using the integrated terminal and organizing your project folders — that turn a collection of installed tools into a genuinely comfortable place to write code.
A “coding environment” sounds more complicated than it actually is in practice. At its core, it’s just: an editor to write in, a way to run your code, and a sensible folder structure to keep everything organized as your projects grow past a single file.
The Three Pieces of a Basic Coding Environment
According to freeCodeCamp’s guide to setting up a development environment, a working setup generally needs a code editor, a command line interface, and — as projects grow — a version control system and package manager. As a beginner, the first two are what actually matter right now; the other two become relevant once you’re comfortable with the basics.
Here’s the beginner-friendly version of that same list:
- A code editor — covered in our code editors guide, with VS Code as the common default.
- A way to run your code — for Python, this means Python itself installed and accessible from a terminal; for JavaScript, it means a web browser (and eventually Node.js).
- A terminal you’re comfortable opening — most modern editors have one built in, which removes the need for a separate application.
Setting Up VS Code for a Specific Language
A fresh VS Code install is a general-purpose text editor until you add support for the language you’re actually learning. According to Microsoft’s official Python tutorial for VS Code, installing the Python extension turns VS Code into a genuinely capable Python editor, adding features like code completion, debugging, and the ability to run files directly from inside the editor.
To install a language extension in VS Code: open the Extensions panel (usually a icon in the left sidebar, or Ctrl/Cmd+Shift+X), search for the language you’re learning (“Python” or “JavaScript,” for example), and click Install on the official extension from Microsoft. This same process applies to virtually any language — search, find the official or most popular extension, install it.
Using the Integrated Terminal
Every modern code editor, including VS Code, includes a built-in terminal — a text-based way to run commands without opening a separate application. You can open it in VS Code with the keyboard shortcut Ctrl+` (backtick) or through the View menu.
As a beginner, you’ll mostly use the terminal for one thing at first: running the file you’re currently working on. For Python, that means typing python3 filename.py (or python filename.py on Windows) and pressing Enter. Getting comfortable with this single command is enough to start; more advanced terminal usage can wait until you actually need it.
Organizing Your Project Folder
It’s worth building good habits early, even for tiny practice projects. Create a dedicated folder for your coding projects — something like “coding-projects” in your Documents folder — and create a new subfolder inside it for each separate project you start. Opening that project’s folder directly in VS Code (File → Open Folder) rather than opening individual files one at a time makes your editor aware of the whole project, which unlocks better features like project-wide search and file navigation in the sidebar.
A simple structure like this works fine for early projects:
coding-projects/
first-python-project/
main.py
first-web-project/
index.html
style.css
script.jsConfirming Everything Works Together
Once your editor, language, and terminal are set up, it’s worth running one genuinely complete test before moving on. For Python: open your project folder in VS Code, create a file named main.py, type print("Hello, world!"), open the integrated terminal, and run python3 main.py. Seeing “Hello, world!” printed out confirms every piece — editor, language installation, and terminal — is correctly connected.
For web development, the equivalent test is creating an index.html file with some basic content (see our HTML basics guide for a starter template) and opening it directly in your browser to confirm it renders as expected.
A Few Extra Extensions Worth Installing Early
Beyond the core language extension, a couple of small additions make everyday coding noticeably smoother without adding real complexity. A code formatter — Prettier is the most common choice for web languages, while Python’s ecosystem has options like Black — automatically cleans up spacing and indentation every time you save a file, so you don’t have to think about formatting style manually while you’re still learning the language itself.
A linter is another small addition worth knowing about: it’s a tool that scans your code as you write and flags likely mistakes — an unused variable, a missing closing bracket, an obvious typo — before you even try running the code. Most language extensions either include basic linting automatically or prompt you to install a companion extension for it, so you often don’t need to seek this out separately.
It’s worth resisting the temptation to install dozens of extensions right away, though. A handful of well-chosen ones — language support, a formatter, maybe a linter — cover what a beginner actually needs. Extensions for advanced frameworks, cloud deployment, or specialized workflows can wait until a specific project actually calls for them.
Keeping Your First Environment Simple
It’s easy to fall into a trap of endlessly tweaking settings, themes, and keyboard shortcuts before writing any real code — a habit sometimes only half-jokingly called “productive procrastination.” The good news is that VS Code’s defaults are genuinely reasonable out of the box, and nothing about the default setup will hold back your ability to learn a language.
A better use of early time is simply working through small, real exercises inside your new environment — a few lines of Python, a simple HTML page — rather than continuing to adjust settings that have little bearing on whether your code actually runs.
Common Questions Beginners Ask About Setting Up an Environment
Do I need a different setup for Python versus JavaScript? Mostly just the language extension changes — the editor, terminal usage, and folder organization habits carry over between languages almost unchanged.
Should I set up version control (Git) right away? Not necessarily on day one. It’s a genuinely useful habit to build once you’re comfortable with the basics, but as MDN’s guide to installing basic software suggests for beginners, starting with just a solid code editor and modern browsers is enough to get going — you can layer in version control once you’re past the absolute basics.
What if my terminal says “command not found” when I try to run Python? This almost always traces back to installation — either Python wasn’t added to your system’s PATH (a common Windows issue covered in our installation guide), or the terminal needs to be reopened after installing Python so it picks up the change and recognizes the newly available command.
Is it normal to feel overwhelmed by all these small setup steps? Yes, and it’s genuinely temporary. Every one of these steps — installing an extension, opening a terminal, organizing a folder — becomes automatic within the first few projects, at which point your environment stops being something you think about at all.
Quick-Reference Coding Environment Setup Guide
- Editor — VS Code (or your chosen alternative), with the relevant language extension installed.
- Language — Python, Node.js, or whatever your project needs, installed and verified via the terminal.
- Terminal — use your editor’s built-in terminal rather than a separate application, at least at first.
- Project folders — one dedicated parent folder, with a subfolder per project.
- Open folders, not files — opening the whole project folder in your editor unlocks better navigation and search.
- Confirm with a real test — a working “Hello, world!” run end-to-end confirms your setup is genuinely connected.
Conclusion
A coding environment doesn’t need to be elaborate to be effective — an editor with the right language extension, a terminal you’re comfortable opening, and a sensible folder structure cover the vast majority of what a beginner actually needs for months of learning. The goal isn’t a perfectly optimized setup; it’s one you understand well enough to stop thinking about, so your attention goes to the code itself.
With your environment confirmed working end to end, you’re ready to actually start building — whether that’s working through Python fundamentals or continuing with HTML, CSS, and JavaScript, using the exact same setup you just put together.
In the next guide in this series, we’ll cover the terminal in a bit more depth — the handful of commands worth knowing beyond just running a file, which will make navigating your projects and files noticeably faster once they’re second nature.
Explore More Tools & Setup Guides →
Alex Carter is a senior software developer with years of hands-on experience building real-world applications. After watching countless beginners give up on programming simply because most tutorials assumed too much prior knowledge, Alex started Vandutz Academy to do things differently — breaking every concept down into clear, judgment-free, step-by-step lessons. When not writing, Alex is probably debugging someone else’s code (or their own).