This is the literal first rung: turning a normal laptop into a machine that can create real software. You will install a code editor, Node.js, and Git, open a terminal, and run a command that proves it all works. No prior experience needed — just follow each step in order. It is Windows-first, with quick notes for macOS and Linux, and it is built for building from Nigeria.
Do these in order. Each step is small on its own, and by the end you will have run code you wrote on your own machine.
Your editor is where you read, write, and run code. Get VS Code (free, the most common) or Cursor (an AI-first editor built on VS Code). Go to code.visualstudio.com or cursor.com, download the Windows installer, and run it. During install, tick the boxes for “Add to PATH” and “Open with Code” so it integrates cleanly. On macOS, drag the app into Applications. On Linux, use the .deb or .rpm, or your package manager.
Node.js lets you run JavaScript and modern web tools on your machine, and it comes with npm (the package installer). Go to nodejs.org and download the LTS version (the green, even-numbered one — LTS means long-term support and fewer surprises). Run the installer and click through with the defaults. On macOS you can also use the same installer from nodejs.org; on Linux, prefer nvm (Node Version Manager) so you can switch versions without sudo.
Git tracks every change you make and lets you push your work online so an outage or a dead laptop never erases it. On Windows, download from git-scm.com and accept the defaults — the installer also gives you Git Bash, a friendlier terminal. On macOS, running git --version once will prompt you to install the developer tools. On Linux, install it with your package manager (for example sudo apt install git).
The terminal is a text window where you type commands. On Windows, open Windows Terminal or Git Bash from the Start menu (avoid the old Command Prompt for these steps). On macOS, open Terminal from Spotlight. On Linux, open your terminal app. You can also use the built-in terminal inside VS Code or Cursor: View → Terminal, or press Ctrl and the backtick key together.
Type each command below and press Enter. Each one should print a version number. If you see versions for all three, your machine is ready to build. If a command says it is not recognised, close and reopen the terminal first — installers often need a fresh window to take effect.
node -v
npm -v
git --versionNow make Node actually do something. Create a folder, move into it, and start a project. The first command makes a package.json (the file that tracks your project); the second prints a line so you can see Node run your own code. When the second command prints your message, you have just run code you wrote on your own PC.
mkdir my-first-build
cd my-first-build
npm init -y
node -e "console.log('My PC is ready to build.')"node -v, npm -v, and git --version each prints a version number instead of an error. That is the whole bar. You do not need to understand the numbers yet — you only need them to appear.Almost every first-time setup hits one of these. None of them mean your PC is broken or that you are not cut out for this — here is the fix.
The terminal was open before the install finished, so it has not picked up the new program. Close every terminal window and open a fresh one, then run the version command again. If it still fails, reinstall and make sure the “Add to PATH” option is ticked.
On a shared or work laptop you may not be an administrator. Right-click the installer and choose “Run as administrator,” or ask whoever owns the machine. On Linux, that is what sudo is for. Avoid pasting random sudo commands from the internet without reading them first.
Some antivirus tools flag developer installers as suspicious. Download only from the official sites — code.visualstudio.com, cursor.com, nodejs.org, git-scm.com — and allow the file if your antivirus prompts you. Never grab these tools from a random mirror or a cracked link.
This is almost always the network dropping mid-download. Wait for a stable connection, then run the command again — npm picks up where it left off. If it stays broken, run npm cache clean --force and try once more.
Data and power are real constraints. Here is how to do this setup without stress.
These four installers are the only big downloads in this guide — grab them when your data or Wi-Fi is strong, ideally all in one sitting. After that, the editor, Node, and Git live on your machine and work offline. Keep the installer files in a folder so you can reinstall later without re-downloading.
Set your editor to auto-save and commit to Git often so an outage never costs you work. A charged power bank or small UPS buys you the few minutes you need to save and shut down cleanly. Because Git pushes your work online, even a dead laptop will not erase your project.
You only do this setup once per machine. Every tool, course, and challenge after this assumes you can open a terminal and run a command — so getting this rung right makes everything that follows faster.