Your Toolkit — Part 2: Git & GitHub, Gently

maang.io AI-Native Builder Series

What is this?

You've played a video game with save points. You reach one, the game saves, and now you can take a risk — fight the boss, explore the scary cave — knowing that if it goes wrong, you reload the last save and you're fine. The save points turn fear into freedom. You try bold things because you can't really lose progress.

Git is save points for your code. It's a tool that takes a permanent snapshot of your entire project whenever you ask, and keeps every snapshot forever. Made a change that broke everything? Travel back to a snapshot from ten minutes ago. Want to try a wild idea without risking your working app? Branch off into a parallel save and merge it back only if it works. Git turns "oh no, I broke it and I can't undo" — the single most demoralizing moment for a beginner — into "no problem, roll back." GitHub is the partner to Git: it's the website where your snapshots live online, so your code is backed up, shareable, and the place your team works together.

The one-line idea: Git is a time machine that saves snapshots of your code so you can never truly lose work, and GitHub is the online home where those snapshots live and your team collaborates.

This chapter is gentle and conceptual — we're building the mental model, not drilling commands. As the director, you mostly need to understand what Git is doing for you and why it matters; your AI partner will often run the exact commands. Let's meet the time machine.