Troy's Tech Corner

Who this is for: Anyone setting up their environment to learn coding — whether you're picking up your very first language or levelling up from the basics. This guide covers not just what to install, but why each piece matters so you understand the tools you're using.

What Is a Coding Learning Station?

A Coding Learning Station is a purposefully set-up workspace — both the physical desk you sit at and the software tools on your screen — designed to make learning to code as smooth and distraction-free as possible.

Getting this right at the start matters more than most people realise. Trying to learn while fighting a broken environment, hunting for the right resource, or sitting in a chair that hurts your back after an hour adds friction that has nothing to do with coding. Remove that friction first, and the actual learning becomes much easier.

This guide walks you through every layer: choosing a language, setting up your editor, installing the right tools, and building habits that lead to real progress.

Step 1: Choose Your First Language

The most important rule here: pick one language and stick with it. Jumping between languages before you're comfortable is one of the most common reasons beginners stall out.

Here's a simple starting point based on your goal:

Web development (front-end) — Start with HTML and CSS to learn how pages are structured and styled, then move to JavaScript to make them interactive. This is the clearest on-ramp into web development.
Web development (full-stack) — JavaScript (via Node.js) or Python. Both can handle front-end and back-end work.
Data science, AI, or machine learning — Python. It's the dominant language in this field by a wide margin.
iOS app development — Swift, Apple's official language for iPhone and iPad apps.
Android app development — Kotlin, Google's preferred language for Android.
General-purpose / best first language — Python. It reads almost like plain English, has simple syntax, and has one of the largest beginner communities of any language.
Game development — C# if you're using the Unity engine, or GDScript if you're using Godot (an open-source alternative).

💡 Does the language really matter that much? Less than you think long-term — the core concepts of programming (variables, loops, functions, logic) transfer between languages. What matters is getting to grips with those concepts in one language before spreading out. Python or JavaScript are the safest first choices for most people because of the wealth of beginner resources available for both.

Step 2: Set Up Your Code Editor

A code editor is the main tool you'll use every day. Think of it like a word processor, but built specifically for writing code — it understands the language you're working in, highlights your syntax in different colours so it's easier to read, catches errors as you type, and gives you tools that speed up your workflow.

The Recommendation: Visual Studio Code

Visual Studio Code (VS Code) is free, built by Microsoft, and used by millions of developers from beginners to professionals. It supports every major programming language and has a huge library of extensions — add-ons that give it new powers.

Download and install VS Code

Go to code.visualstudio.com, download the version for your operating system, and run the installer.

📸 [Screenshot: VS Code download page with OS options]

Once open, take a moment to get familiar with the layout:

Explorer (left sidebar) — shows your project files and folders
Editor (centre) — where you write your code
Terminal (bottom panel) — a built-in terminal so you can run commands without leaving VS Code
Extensions (left sidebar icon) — your gateway to add-ons

📸 [Screenshot: VS Code interface with Explorer, Editor, and Terminal labelled]

Install the right extensions

Extensions are what take VS Code from a text editor to a proper development environment. Open the Extensions panel (Ctrl+Shift+X on Windows/Linux, Cmd+Shift+X on Mac) and install these:

Python (by Microsoft) — if you're learning Python, this is essential. It adds language support, error highlighting, and a debugger so you can step through your code line by line to find mistakes.
ESLint — if you're learning JavaScript, ESLint reads your code as you type and flags potential errors or bad practices before you even run it.
Prettier — automatically formats your code when you save a file. Consistent formatting makes code far easier to read and debug, and this removes the need to think about it manually.
indent-rainbow — colours your indentation levels differently. Sounds minor, but indentation errors are one of the most common beginner mistakes — especially in Python, where indentation controls the structure of your code.
Error Lens — displays error messages directly inline next to the problem line, so you see what's wrong immediately without hunting through a separate panel.

📸 [Screenshot: VS Code Extensions panel with extensions installed]

Turn on auto-save

Go to File → Preferences → Settings, search for auto save, and set it to afterDelay. This saves your file automatically a moment after you stop typing, so you never lose work by forgetting to hit Ctrl+S.

Step 3: Install Your Language Runtime

A code editor is just where you write your code. To actually run it, your computer needs the language runtime — the software that reads your code and executes it.

If you chose Python

Go to python.org/downloads and download the latest stable version (3.12 or higher)
Run the installer
Windows users only: on the first screen of the installer, check the box that says "Add Python to PATH" before clicking Install

📸 [Screenshot: Python installer with "Add to PATH" checkbox highlighted]

💡 What is PATH and why does it matter? PATH is a list your operating system checks whenever you type a command in the terminal. If Python isn't on the PATH, your terminal won't know what you mean when you type python3 — it'll just say "command not found." Adding Python to PATH during installation fixes this automatically.

Once installed, verify it worked by opening a terminal and running:

python3 --version

You should see something like Python 3.12.0. If you do, you're good to go.

If you chose JavaScript / Node.js

JavaScript runs natively in browsers, but to run it outside a browser (for back-end work or tooling), you need Node.js — a runtime environment that lets JavaScript run on your computer directly.

Go to nodejs.org and download the LTS version (LTS stands for Long Term Support — it's the stable version recommended for most users)
Run the installer with default settings
Verify in a terminal:

node --version
npm --version

💡 What is npm? npm stands for Node Package Manager. It installs alongside Node.js and is how you add third-party libraries to your projects — think of it as an app store for code packages. Nearly every JavaScript project uses npm to manage its dependencies.

Step 4: Set Up Version Control with Git

Git is software that tracks every change you make to your code over time. It keeps a full history of your project so you can see what changed, when, and why — and roll back to an earlier version if something breaks.

This might sound like overkill when you're just learning, but building the Git habit early is one of the most valuable things you can do. It's a universal skill used on virtually every professional software project.

Install Git

Mac: Open Terminal and run git --version. If Git isn't installed, macOS will prompt you to install it automatically.
Windows: Download the installer from git-scm.com and run it with default settings.
Linux: Run sudo apt install git in the terminal.

Configure Git with your name and email

Git attaches your name and email to every change you record. Run these two commands in the terminal, replacing the details with your own:

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Create a GitHub account

Git lives on your computer. GitHub is a website where you store your Git projects online — think of it as cloud backup for your code, plus a portfolio of everything you've built.

Go to github.com and create a free account.

📸 [Screenshot: GitHub signup page]

Create your first repository

A repository (or "repo") is a Git-tracked project folder. To create one for your learning work:

On GitHub, click the New button
Name it learning-projects
Set it to Public and check "Add a README file"
Click Create repository

Then copy it to your computer with this command (replace your-username with your actual GitHub username):

git clone https://github.com/your-username/learning-projects.git

This creates a folder on your computer that's connected to GitHub. When you want to save a snapshot of your work, you commit your changes locally, then push them to GitHub — your online backup.

💡 What's the difference between Git and GitHub? Git is the tool — it runs on your computer and tracks changes. GitHub is the hosting service — it stores your Git history online and makes it accessible from anywhere. They're separate things that work together. Other hosting services like GitLab and Bitbucket serve the same purpose as GitHub.

Step 5: Choose Your Learning Resources

The internet has an overwhelming amount of coding tutorials. The key is to pick one primary resource and follow it consistently rather than jumping between several — a common trap that creates the feeling of progress without actually building solid foundations.

Free platforms worth using:

freeCodeCamp (freecodecamp.org) — Structured, project-based curriculum covering web development, JavaScript, and Python. Completely free with certifications.
The Odin Project (theodinproject.com) — A highly regarded full-stack web development curriculum. More challenging than most free options, but produces solid results.
CS50 (cs50.harvard.edu) — Harvard's free introductory computer science course. Covers fundamentals that apply to any language. Excellent if you want to understand why things work, not just how to use them.
Exercism (exercism.org) — Practice problems with optional human mentoring. Good as a supplement once you've got the basics.

Paid platforms worth the money:

Scrimba — Unique format where you can edit code directly inside the video. Particularly good for front-end development.
Zero to Mastery — Well-structured courses with a focus on career-ready skills. Good pacing for beginners.

Books:

Automate the Boring Stuff with Python by Al Sweigart — Free online, and one of the most practical beginner Python books available. Focuses on real-world tasks rather than abstract exercises.
Eloquent JavaScript by Marijn Haverbeke — Free online and one of the most respected JavaScript learning books. Slightly more challenging, but worth it.

Step 6: Build a Practice Routine

Consistency matters far more than the number of hours you put in on any single day. Thirty focused minutes every day will get you further than a four-hour session on a Saturday followed by nothing for a week.

A simple daily structure (30–60 minutes):

5 minutes — Review what you wrote yesterday. Read through your code and your notes. This spaced repetition is one of the most effective ways to retain what you've learned.
20–40 minutes — Work through your current course or tutorial. When you hit an explanation you don't understand, don't just skip it — pause, re-read it, look it up separately if needed, and make sure you actually follow it before moving on.
10–15 minutes — Write code yourself without copying from the tutorial. Even modifying an example slightly — changing the values, adding a feature — is far more effective than following along passively.
5 minutes — Commit your work to Git with a short message describing what you did. This builds the habit and gives you a satisfying record of your progress.

Weekly: Try to build one small project using what you learned that week. A tip calculator, a to-do list, a number guessing game, a quiz — it doesn't need to be impressive. Building something yourself is what makes concepts actually stick.

💡 Why does building projects matter so much? Tutorials teach you how tools work in isolation. Projects force you to combine those tools to solve a real problem — which is much closer to what real programming looks like. Most developers find that their understanding doubles when they move from following tutorials to building something of their own.

Step 7: Set Up Your Physical Workspace

This is easy to overlook, but your physical environment directly affects your ability to focus and stay comfortable during longer sessions.

The basics:

Monitor height — the top of your screen should be at or just below eye level. Looking down for extended periods strains your neck.
Lighting — position your screen to avoid glare. A desk lamp behind your monitor gives ambient light without shining directly on the screen.
Chair — your feet should be flat on the floor with your knees at roughly a 90-degree angle. Back support matters more the longer you sit.
Keyboard and mouse — a full-size keyboard is easier to type on for extended sessions than a compact one. Wireless is fine.

Useful upgrades when you're ready:

Second monitor — having your course or documentation on one screen while you code on the other removes constant tab switching and genuinely speeds things up.
Noise-cancelling headphones — if you work in a shared or noisy space, these can be transformative for focus.
Standing desk or riser — alternating between sitting and standing during longer sessions reduces fatigue.

📸 [Screenshot: Example two-monitor coding workspace setup]

Troubleshooting

❌ "Command not found" when running Python or Node

Your language runtime is installed but the system doesn't know where to find it — it's not on the PATH.

Windows: Re-run the installer and make sure "Add to PATH" is checked.
Mac/Linux: Open your shell profile file (.zshrc for Zsh, .bashrc for Bash) and add this line:

export PATH="/usr/local/bin:$PATH"

Save the file, then run source ~/.zshrc (or source ~/.bashrc) to apply the change, or just close and reopen the terminal.

❌ VS Code shows no syntax highlighting for my language

Make sure you have the right extension installed for your language (Step 2), and confirm your file has the correct extension — .py for Python, .js for JavaScript. VS Code uses the file extension to know which language rules to apply.

❌ Git says "fatal: not a git repository"

You're running a Git command from outside your project folder. Navigate into it first:

cd ~/learning-projects
git status

❌ Feeling overwhelmed or stuck

This is completely normal — every developer experiences it. A few approaches that actually help:

Read the error message carefully. Error messages look scary but they're usually telling you exactly what went wrong and where. Copy the message into a search engine — someone else has almost certainly hit the same issue.
Explain the problem out loud. Walk through what your code is supposed to do, line by line. This is called rubber duck debugging (named after the practice of explaining your code to a rubber duck). Verbalising the problem often reveals the solution before you even finish the sentence.
Step away. A 10-minute break, a short walk, or even sleeping on a problem genuinely works. Your brain continues processing in the background.
Ask for help. Stack Overflow, Reddit's r/learnprogramming, and Discord communities for your specific language are full of people who were beginners recently and remember what it felt like.

Staying Motivated

The biggest drop-off in learning to code happens between the first few weeks of excitement and the point where things actually start clicking. A few things that help bridge that gap:

Build things you actually care about. Even a small, silly project you're genuinely interested in beats abstract exercises every time. The motivation to get it working carries you through the frustrating parts.
Track your streak. GitHub's contribution graph shows a green square for every day you commit code. Keeping the streak going is a surprisingly effective motivator.
Join a community. Find a Discord server or subreddit for your language. Seeing other beginners working through the same problems — and celebrating when things finally work — makes a real difference.
Acknowledge progress. Finishing a chapter, understanding a concept that confused you last week, fixing a bug you've been staring at for an hour — these are genuine wins worth recognising.

Where to Go Next

Once you're comfortable with the fundamentals of your chosen language, here's what's worth exploring:

Frameworks — React for JavaScript front-end, Express or Next.js for JavaScript back-end, Django or Flask for Python. Frameworks give you pre-built tools so you don't have to build everything from scratch.
Databases — almost every real application stores data. Start with SQLite (simple, no setup), then move to PostgreSQL when you're ready for something more robust.
APIs — learn how to connect your code to external services. A weather app, a currency converter, or a news feed all work by pulling data from APIs.
Deployment — put your project on the internet. Netlify and Vercel make this straightforward for front-end projects; Railway works well for back-end apps.
Open source — once you're building confidence, contributing to an open source project you actually use is one of the best ways to level up fast.

Last updated: February 2026

Coding Learning Station Guide