You've probably heard "just learn web development" a hundred times, and nobody ever explains what that covers. So let's skip the explaining for a minute. By the end of this post you'll have built a small page with a working button, using a text editor and a browser.

TL;DR

  • Every website runs on 3 browser languages: HTML for structure, CSS for style, JavaScript for behaviour.
  • Web development splits into 2 halves. Frontend is what runs in your browser, backend is what runs on a server.
  • You can write a working, interactive page in under 20 lines of code with nothing but a text editor and a browser.
  • Start with frontend, not backend. You see results instantly, and that feedback keeps beginners going.

Build the page first

Open any text editor (Notepad works, though VS Code is better and free). Create a file called index.html and paste this in:

<!DOCTYPE html> <html> <head> <title>My first page</title> </head> <body> <h1>Hello, I'm learning to code</h1> <p id="message">Nothing has happened yet.</p> <button>Click me</button> </body> </html> 

This is pure HTML: a heading, a paragraph with an ID so we can find it later, and a button. Save it, then double-click the file. It opens in your browser.

One thing that trips up beginners on this exact step: the file quietly saves as index.html.txt. If double-clicking opens a text file instead of a page, that's why. Rename it and try again.

It's plain. Let's dress it up. Add this inside the <head>, just under the title:

<style> body { font-family: sans-serif; max-width: 600px; margin: 40px auto; } button { background: #2563eb; color: white; padding: 10px 20px; border: none; border-radius: 6px; } </style> 

That's CSS. It centres your page, swaps the font, and turns the button blue with rounded corners. Save and refresh.

Now the button needs to do something. Add this just before the closing </body> tag:

<script> document.querySelector("button").addEventListener("click", function () { document.getElementById("message").textContent = "You just wrote JavaScript."; }); </script> 

That's JavaScript. It finds the button, listens for a click, and changes the paragraph's text when one happens.

Refresh. Click the button.

You just did frontend web development. Structure, style and behaviour: the same three layers every site on the internet uses. Netflix's homepage is this, scaled up by a few hundred thousand lines and a lot of people.

If it didn't work, open your browser's developer tools (right-click, then "Inspect", then the Console tab). The error message will usually tell you the exact line. Nine times out of ten it's a missing quote or a typo in a name. Fixing it is your first real debugging session.

So what is web development?

It's the work of building the websites and web apps you use every day: the parts you see, the parts you don't, and the code that connects them. A one-page portfolio counts. So does an online banking app, and everything in between.

The job has two sides. One is what you see: text, buttons, layouts, the menu that slides out on your phone. The other is invisible: the server that checks your password, the database that remembers your order, the logic that decides what to show you.

You don't need a computer science degree to understand any of it. You need a mental model. Then you need to build things.

The mental model: what happens when you open a page

Everything else hangs off this, so hold onto it.

You type zamacademy.com into your browser and press Enter. Your browser (the client) sends a request across the internet to a computer somewhere else (the server). The server sends back files. Your browser reads those files and draws the page on your screen.

Those files are mostly written in the three languages you just used:

Language What it does Think of it as
HTML Defines the content and structure The skeleton
CSS Controls colours, fonts, spacing, layout The clothes
JavaScript Makes things respond when you click, type or scroll The muscles

I wrote a longer piece on the difference between HTML, CSS and JavaScript if you want it. For now, the table is enough.

Then there's the server side. Sometimes the server sends the same files to everyone. Often it doesn't. When you log into your email, the server looks you up in a database, grabs your messages, and builds a page just for you. That work is backend development.

Frontend vs backend

Most developers lean towards one half.

Frontend is everything that runs in the browser. Frontend developers write HTML, CSS and JavaScript, and usually a framework like React or Vue once they're past the basics. They care about layouts, accessibility, page speed and how it feels to click around.

Backend is everything that runs on the server. Backend developers write code in Python, JavaScript (via Node.js), PHP, Java, C# or similar. They build APIs, design databases, handle logins and make sure one user can't see another user's data.

Full-stack developers do both. It's a common job title, though most full-stack people are still stronger on one side.

Frontend Backend
Runs on The user's browser A server
Core languages HTML, CSS, JavaScript Python, Node.js, PHP, Java, C#
You see results Instantly, on screen Through logs, APIs, test output
Typical bug Layout breaks on mobile Data saves wrong, or not at all

My opinion: start with frontend. Not because it's easier (good CSS is surprisingly hard) but because you see what you build. You change a colour, refresh, and it's different. That instant feedback does more for a tired beginner's motivation than any pep talk.

Backend comes next, and that's where web development gets really interesting. Python is a lovely first backend language. There's more on it in the web development learning path.

What a web developer does all day

Less typing than you'd think. A lot more reading.

On a normal day a web developer reads existing code to work out why something broke. Then they write new features, test them in a few browsers, and review other people's changes. They spend real time in the browser's developer tools, inspecting why a button sits 4 pixels too low on mobile.

If we were pair-programming, here's what I'd tell you: most of the job is debugging, and nobody tells beginners this. You'll write ten lines, and one of them won't work. You'll spend 40 minutes discovering you typed getElementByID instead of getElementById. Capital D versus lowercase d. Everyone does this. It's the job, not proof you're bad at it.

Developers also talk to people. Designers hand over mockups. Product managers explain what the feature should do. A developer turns all that into working code and pushes back when something won't work as drawn.

Web developer vs web designer

People mix these up constantly.

A web designer decides how a site should look and feel. They work in tools like Figma, thinking about typography, colour, spacing and how a user moves through a page. Their output is a mockup.

A web developer turns that mockup into a working site. Their output is code that runs.

There's overlap. Many frontend developers have a decent eye, and many designers know some HTML and CSS. But if you enjoy making things work more than making things pretty, you're leaning developer.

Is it still worth learning in 2026?

Fair question, with AI tools writing code now. My honest take: AI is very good at producing the snippet you just asked for. It's much worse at knowing whether that snippet belongs in your project, why it broke, or what the client actually meant. That judgement is the skill employers pay for.

For current pay and outlook data, skip any number quoted in a blog post (including this one) and read the US Bureau of Labor Statistics' occupational profile for web developers and digital designers. If you're wondering where this could lead, here are realistic jobs you can get after learning to code.

The order I'd learn it in

Most beginners stall here. Not because the material is too hard, but because there's too much of it and no order.

  1. HTML and CSS first. Build three or four static pages: a profile, a recipe page, a fake landing page for a café.
  2. Then JavaScript. Make those pages respond. Buttons, forms that check input, a to-do list.
  3. Then one backend language. Python or Node.js. Learn to save data and read it back.
  4. Build a real project end to end. Something with a frontend, a backend and a database, even a small one.

Keep MDN Web Docs open the whole time. It's the reference working developers use, and it's free.

The biggest trap is watching tutorials instead of building. You'll feel productive, then open a blank file and freeze. If that sounds familiar, read about how to escape tutorial hell. The fix is always the same: build small things that are slightly too hard for you.

Your next step

Take the page you just built and change it. Make the button count how many times it's been clicked. Add a second button that resets the count. You'll have to look things up, and you'll hit at least one error. Good. That's the work.

When you're ready for something bigger, pick from these first coding project ideas that are actually doable.

And if you'd rather not figure out the order alone, ZAM Academy pairs you with a working software engineer for 1-on-1 sessions and a roadmap built around you. Your first two classes are free.

Adapted from What Is Web Development? A Beginner's Guide on the ZAM Academy blog.