GitHub

Here's the thing that confuses everyone, and it tripped me up for years: Git and GitHub are not the same thing. The names are almost identical. The jobs are not.

Git lives on your computer. It's the time machine that tracks every snapshot of your work, sitting quietly on your laptop. GitHub is where that work goes to live online. It takes a copy of your project, history and all, and parks it in the cloud where it's backed up and other people can see it.

The cleanest way I've found to say it: think Google Drive, but built specifically for code. Your files live on your machine, and a synced copy lives somewhere safe online that the whole team can reach.

Two reasons it runs the entire software world.

1. Backup and teamwork. If your laptop dies in a coffee spill tomorrow, your project doesn't. It's sitting on GitHub, untouched. And when a team builds together, everyone works off the same online copy instead of mailing files around like it's 2004. You push your snapshots up, your teammate pulls them down, and you're both working on the same living thing.

2. It's the town square of software. Millions of public projects sit on GitHub, open for anyone to read, learn from, or build on. It's where the world's code hangs out in public.

A few words you'll bump into the second you start poking around:

• Repo (short for repository): just the folder for one project, with its whole history attached. "Where's the repo?" means "where does this project live?"
• Push: send your latest snapshots from your laptop up to GitHub.
• Pull: grab the latest snapshots down from GitHub to your laptop.
• Clone: make your own full copy of someone else's project so you can run it and tinker.

You don't have to memorize these. But when an AI agent says "I'll push this up" or "let me clone that repo," you'll know it's just moving copies between your machine and the cloud.

Where you've already touched it without knowing. When you hear a company is open source, GitHub is usually where it's hosted, sitting right there for anyone to inspect. And when an AI agent goes to install a tool for you, it very often pulls it straight from GitHub. The thing builds half its toolbox out of stuff hosted there.

One warning that bears repeating, because it bites people for real money.

Most GitHub projects are public. The entire internet can read them. So the rule from the very first day of this thing stands:

Never let an API key get committed and pushed to GitHub.

There are bots that do nothing but scan GitHub all day looking for leaked keys. They find one, and within minutes they're spending your money on your account. Keep your secrets in a separate hidden file, never in the code that goes up. (More on exactly how that drawer works on its own day.)

Git is the engine. GitHub is the garage everyone shares.