Ask someone what a website is and they'll point at the screen. That's fair — the screen is where the website lives for them. But the visible page is only half of the story. Behind every action you take online, two worlds work together: the front end you can see, and the back end you never do.
The front end: everything you can point at
The front end is the part of the website that runs in your browser. HTML gives the page its structure, CSS gives it style, and JavaScript gives it behavior. When a button changes color as you hover, when a menu slides open, when a form warns you about a missing field before you submit — that's the front end doing its job.
The back end: everything that has to be remembered
The back end runs on a server — a computer whose job is to respond to requests. It holds the logic that decides what should happen: check this password, calculate this total, save this order. And it talks to the database, which is where information lives permanently. Your browser forgets everything when the tab closes. The database is how a store remembers your cart tomorrow.
// Your browser asks:
GET /api/products/42
// The server checks the database and answers:
{
"id": 42,
"name": "Handwoven Basket",
"price": 2400,
"inStock": true
}
// The front end renders that data into the page you see.APIs: the language between the two
The front end and back end communicate through an API — an agreed set of requests and responses, usually as structured JSON. The browser asks a precise question ('give me product 42'), the server answers precisely, and the interface turns that answer into something a human enjoys reading. This separation is powerful: the same API can feed a website, a mobile app and a partner's system at once.
The front end is the conversation. The back end is the memory. The API is the language they share.
Understanding both sides changed how I build. A beautiful interface with a fragile backend is theatre. A robust backend with a hostile interface is a machine nobody operates. The craft is in making the two feel like one continuous experience — which is exactly why I love working across the full stack.


