GitHub — What It Is and Why You Need It

The scenario that explains everything

You've spent three weeks building a web application for a client. You make a set of changes one Tuesday — a new feature the client requested. On Thursday the client calls: "I don't like the new version. Can we go back to what we had before Tuesday?"

What do you do?

If you've been saving the project as a folder on your desktop, you're in trouble. You'd have to remember every file you changed, manually undo every edit, and hope you didn't miss anything. Realistically — you can't. You'd tell the client that reverting isn't possible and hope for the best.

Now imagine a second scenario. Three developers are working on the same project simultaneously. One person edits the login page. Another edits the database. A third edits a shared component that both of the others depend on. On Friday, someone pushes their version to the server — and it overwrites the other two people's work.

These aren't edge cases. They happen to every team that doesn't use version control. And Git + GitHub is the solution the entire industry has standardised on.

Git and GitHub are two different things

This distinction trips up almost everyone at first.

Git is the tool installed on your computer that tracks changes to your code. Every time you run git commit, Git takes a snapshot of your project at that exact moment — every file, exactly as it is. It stores a complete history of every snapshot ever taken. If you want to go back to Tuesday, Git can do that in one command.

Think of Git as Excel's Track Changes — but for every file in your project, going back forever, with the ability to jump to any point in history instantly.

GitHub is a website — github.com — that stores your Git history in the cloud. Without GitHub, your history only exists on your laptop. If your laptop is lost, stolen, or breaks, your history goes with it. GitHub is the cloud backup. It's also where you share code with teammates.

Think of GitHub as SharePoint or Google Drive — but instead of storing files that overwrite each other, it stores every version of every file, with a complete record of who changed what and when. Multiple people can work on the same project without destroying each other's work.

Where GitHub fits in your daily workflow

As a developer, your day follows this cycle:

1. Open VS Code — your code editor, where you write code
2. Make changes — add a feature, fix a bug, update a page
3. Commit to Git — save a snapshot with a description of what changed
4. Push to GitHub — send that snapshot to the cloud
5. Deploy — Vercel (your hosting platform) automatically picks up the new version and publishes it

GitHub sits between your laptop and the world. It's the checkpoint every piece of code passes through before it reaches your users.

Why GitHub specifically (not Dropbox, not Google Drive)

Dropbox and Google Drive solve the wrong problem. They sync whatever is currently in a folder. If you save a broken version of a file, they sync the broken version. There's no concept of "this version is good, that version is broken."

GitHub tracks intent. When you commit, you write a message: "Add payment form" or "Fix login bug on mobile." Six months later, you can search your history for "payment" and find exactly when and how that feature was built. You can compare any two versions side by side and see the exact lines that changed.

For client work specifically: GitHub is your proof of work. If a client questions when something was built or changed, the commit history is your timestamped record.

GitHub is also your professional profile

Every developer's GitHub profile is public. Clients, future employers, and collaborators look at GitHub the same way they look at LinkedIn — it shows your history, your projects, and your activity. A well-maintained GitHub profile with real projects is worth more than a CV that claims you know how to code.

Your username matters. Choose a professional name — your real name or something close to it — because it will be in every URL you share.

---

What's in this module

Work through these pages in order. By the end, you'll have a GitHub account set up the way professional developers use it — not just created but properly configured.