You've probably lost work before. A file you spent hours on suddenly disappeared. A change that worked yesterday broke everything today. Maybe you deleted the wrong thing, or your computer crashed, or you just can't remember what you changed.
Git prevents these disasters. It's a tool that saves snapshots of your work automatically and lets you jump back to any previous version. Think of it as an undo button that never stops working, plus a filing system that remembers everything you've ever done to your files.
What Git actually does
Git watches a folder on your computer and tracks every change you make to the files inside. When you tell it to, Git takes a snapshot of everything and stores it permanently. You can take as many snapshots as you want, and Git remembers them all.
Each snapshot gets a unique name (a long string of letters and numbers) and a description you write. Later, you can see exactly what changed between any two snapshots, or jump back to how things looked last week.
This works with any text files: documentation, configuration files, scripts, even novels. If you can edit it in a text editor, Git can track it.
Git vs. GitHub (they're different things)
Git runs on your computer. It's the tool that tracks your changes and stores your snapshots. GitHub is a website where you can upload those snapshots to share with other people or back them up online.
You use Git locally, then push your work to GitHub when you want others to see it or when you want an online backup. GitHub adds features like issue tracking and collaboration tools, but Git itself works fine without it.
Think of Git as your camera and GitHub as Instagram. The camera takes photos whether you post them online or not.
Why you need this
Without Git, you're flying blind. You make a change, something breaks, and you're stuck trying to remember what you did. You might keep backup copies with names like "project_final.txt" and "project_final_v2.txt" and "project_ACTUALLY_final.txt", but that gets messy fast.
Git eliminates this chaos. Every change gets recorded with a timestamp and description. You can see exactly what changed, when, and why. If something breaks, you can pinpoint the exact change that caused it and either fix it or undo it completely.
Git also prevents the "it works on my computer" problem. When you share your work through Git, others get the exact same files you have, with the complete history of how they got that way.
The mental shift
Stop thinking about files as things that exist in one state. Start thinking about them as having a history. Your document isn't just what it looks like right now, it's the accumulation of every change you've made since you started working on it.
Git makes this history visible and navigable. You're not just editing files anymore, you're building a timeline of your work that you can explore, modify, and learn from.
This changes how you work. You'll take more risks because you know you can always go back. You'll try experimental ideas because failure becomes reversible. You'll collaborate more confidently because everyone's working from the same foundation.
In the next step, you'll install Git and set it up properly. Once it's running, you'll never lose work to accidents again.