The tooling landscape is overwhelming when you start. Every tutorial introduces something new, and it is easy to spend weeks installing things instead of building.
The actual minimum is small.
The five you need
1. Visual Studio Code
Free, works on every platform, and what most of the industry uses. It gives you syntax highlighting, autocomplete, error detection before you run anything, integrated Git and a built-in terminal.
Extensions worth having early:
- Prettier — formats your code automatically on save. Ends all formatting decisions permanently, which is more valuable than it sounds.
- ESLint — catches common JavaScript mistakes as you type.
- Live Server — serves your files locally and refreshes the browser on save.
Resist installing thirty extensions. Each one adds startup time and surface area for things to behave oddly.
2. A browser with developer tools
You already have this. Press F12 in Chrome, Firefox or Edge.
This is the most under-taught skill in web development. Learning dev tools properly will do more for your progress than any framework.
The panels that matter:
- Elements — see the live HTML, modify CSS and watch the result instantly. The fastest way to understand why something looks wrong.
- Console — see JavaScript errors and run code against the live page.
- Network — see every request, how long it took, and what came back.
Spend a deliberate afternoon on these early. It pays back continuously.
3. Git
Version control. It records every change, lets you return to any previous state, and lets several people work on the same project.
Start on your first project, not when things get serious. Learning Git on a small project with nothing at stake is far easier than learning it in a panic.
The commands covering most daily use:
git init # start tracking a project
git add . # stage your changes
git commit -m "message" # save a snapshot
git push # send to GitHub
git pull # get others' changes
git status # what has changed
git log # history
That is genuinely most of it. The complicated parts of Git — rebasing, cherry-picking, resolving difficult merges — can wait until you need them.
Pair it with a GitHub account, which hosts your repositories, acts as a portfolio, and can publish static sites for free.
4. A terminal
macOS and Linux have one built in. On Windows, use Windows Terminal with PowerShell, or WSL for a Linux environment.
You need a handful of commands:
cd folder-name # move into a folder
cd .. # move up one level
ls # list files (dir on Windows PowerShell)
mkdir name # make a folder
pwd # where am I
Plus whatever your tools need. It is less intimidating than it looks, and nearly everything in modern development runs through it.
5. Node.js and npm
Node runs JavaScript outside the browser. npm, which installs with it, downloads the packages your project depends on.
Even if you are only writing HTML and CSS at first, nearly every tool you will eventually use arrives through npm.
node --version # check it installed
npm install name # add a package
npm run dev # run the project's dev script
That is the whole list
With those five you can build a real website, version it, and publish it. Everything else is an improvement on that foundation rather than a requirement.
What can wait
A framework. Learn HTML, CSS and JavaScript properly first. Frameworks are easier once you understand what they are abstracting over, and beginners who learn React before JavaScript get stuck the first time something behaves unexpectedly.
TypeScript. Excellent and worth learning. After you are comfortable with JavaScript, not before.
Docker. Solves a problem you do not have yet.
A testing framework. Add it the first time you break something and do not notice for a week. That experience teaches the value better than any tutorial.
A CSS framework. Write plain CSS until you understand the box model, flexbox and grid. Tailwind is excellent and it is easier to learn when you know what each utility maps to.
A database. When you have something to store.
The order to learn
- HTML — structure. A week or two.
- CSS — layout and appearance. Longer. Flexbox and grid specifically.
- Git — from your first project.
- JavaScript — properly. Variables, functions, arrays, objects, the DOM, events, async. This takes months and is the foundation for everything after.
- The terminal and npm — picked up alongside.
- A framework — once JavaScript is comfortable.
- Everything else — in response to actual problems.
Step four is where people rush and where rushing costs most. A solid JavaScript foundation makes every framework easy; a weak one makes all of them confusing.
On AI assistants
They are now part of how professional development happens, and the honest assessment for beginners is mixed.
They are genuinely excellent for explanation. Paste an error message and ask what it means. Ask why a piece of code works the way it does. Ask for three approaches to a problem with the trade-offs. This is a patient tutor available at any hour and it is a real advantage over learning five years ago.
They are risky for generation. Accepting code you do not understand produces the feeling of progress without the skill, and you discover the gap the first time something breaks in a way the assistant cannot fix.
A reasonable rule while learning: use AI to explain, write the code yourself. Once you can reliably tell good code from bad, use it for generation too.
Build something
The most important advice and the least technical.
Tutorials create the illusion of competence. Building something nobody told you how to build creates the actual thing. Pick something small and real — a personal site, a tool that solves a minor annoyance of your own — and finish it.
You will get stuck. Getting unstuck is the skill.
If you are learning and want a view on what to focus on next, get in touch — we are happy to point people in a useful direction.
