What is Version Control?
The system that tracks changes to files over time, preventing the chaos of 'final_v2_real.txt'.
What is Version Control?
Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
Before version control, developers relied on making copies of entire project folders (e.g., project_final, project_final_real, project_final_v3_DO_NOT_TOUCH). Git solves this by storing snapshots of your project.
Why it matters
In a professional environment, you are rarely working alone. Version control allows multiple developers to work on the exact same codebase simultaneously without overwriting each other's work.
It also acts as an ultimate safety net. If you introduce a bug, you can instantly time-travel backward to a working state.
How it works (The Git Model)
Unlike older systems (like SVN) that stored changes as a list of file-based patches, Git thinks of its data more like a series of snapshots of a miniature filesystem.
Every time you commit, Git takes a picture of what all your files look like at that moment and stores a reference to that snapshot. If files haven't changed, Git doesn't store the file again, just a link to the previous identical file.
Check yourself
Pick an answer to lock it in, then read why. Getting one wrong is part of how it sticks.
Remember this
- Git is the local software; GitHub is the cloud host.
- Git works completely offline.
- Git stores data as snapshots, not a list of changes.
Done with this concept?
Mark it complete to track your progress. No login needed.