Skip to content

Glossary

One-sentence definitions for every term used across the roadmap. Skim it, then come back whenever a word stops making sense.

A way for one program to ask another for something (e.g. payments via Stripe).

A password that grants access to someone else’s service — keep it secret.

Proving who a user is — “log in with email,” “sign in with Google.”

The logic and rules that run on the server, out of the user’s sight.

A parallel version of the project for experimenting without breaking the main one.

The thing the user touches — a browser or a phone app.

A saved snapshot of your project at a point in time, with a short description.

Where data (users, orders, content) is stored for the long term.

Publishing your app to a remote server so it’s reachable at a link.

The environment where you experiment — usually localhost.

The exact set of changes between two versions of the code.

The internet’s phone book: it translates a domain name into a server’s address.

A human-readable address (myapp.com) instead of a numeric IP.

A file of secrets kept out of Git, separating private config from public code.

What the user sees and interacts with — buttons, screens, layout.

A “time machine” tool on your computer that saves snapshots of your code.

A website that stores your Git project online, for backup, sharing, and deploys.

When an AI states something false with full confidence — a property to guard against.

A service (Vercel, Netlify, Railway, Render) that turns your GitHub code into a live site.

Your own computer acting as a private server, reachable only by you.

The copy of your code on your machine (local) vs the copy on GitHub (remote).

A numbered “door” on a computer (e.g. :3000) that a program listens on.

The live version of your app that real users use.

A running program; your local app only works while its process is running.

The instruction and context you give an AI to get a result.

Bringing changes down from GitHub to your computer.

Sending your changes up from your computer to GitHub.

A project folder under Git’s control — one project, one repo.

Returning the code to an earlier, working snapshot.

A computer on the internet that stores data and answers requests, running 24/7.

A text-based way to give your computer commands.