Why Git mental model (snapshots not diffs)? - Purpose & Use Cases

The Big Idea

What if you could see your entire project's history like flipping through a photo album instead of a messy list of changes?

The Scenario

Imagine you are writing a long essay by hand and every time you make a change, you only write down the differences from the last version instead of the whole page.

Later, you want to see the full essay at a certain point, but you have to piece together all the tiny changes manually.

The Problem

This way is slow and confusing because you must remember every small change and how they fit together.

It's easy to lose track or make mistakes when trying to reconstruct the full essay from just the differences.

The Solution

Git uses snapshots instead of diffs, like taking a full photo of your essay every time you save.

This means you can quickly see the entire state of your project at any moment without piecing together changes.

Before vs After

✗ Before

save_diff(change1)
save_diff(change2)
... // must apply all diffs to see full file

✓ After

save_snapshot(version1)
save_snapshot(version2)
... // each snapshot is a full picture

What It Enables

This lets you easily jump back to any version and understand your project's history clearly and quickly.

Real Life Example

When fixing a bug, you can instantly open the full code as it was before the bug appeared, without reconstructing changes step-by-step.

Key Takeaways

Manual diff tracking is complicated and error-prone.

Git's snapshot model stores complete project states.

This makes version control faster, clearer, and more reliable.

Practice

1. What does Git save when you run git commit?

easy

A. A backup copy of your entire computer

B. Only the changes made since the last commit

C. A list of all commands you typed

D. A snapshot of all your files at that moment

Solution

1. Step 1: Understand what git commit does

   It records the current state of your project files as a snapshot.

2. Step 2: Differentiate snapshot from changes

   Unlike some systems, Git saves the whole snapshot, not just the changes.

3. Final Answer:

   A snapshot of all your files at that moment -> Option D

4. Quick Check:

   Git saves snapshots, not diffs [OK]

Hint: Remember: Git snapshots whole files, not just changes [OK]

Common Mistakes:

• Thinking Git saves only changes (diffs)
• Confusing commit with backup
• Believing commit saves command history

2. Which of the following is the correct command to create a snapshot in Git?

easy

A. git snapshot

B. git save

C. git commit

D. git backup

Solution

1. Step 1: Recall Git commands for saving work

   The command to save a snapshot is git commit.

2. Step 2: Verify other options

   Commands like git snapshot, git save, and git backup do not exist in Git.

3. Final Answer:

   git commit -> Option C

4. Quick Check:

   git commit creates snapshots [OK]

Hint: Use git commit to save snapshots [OK]

Common Mistakes:

• Using non-existent commands like git save
• Confusing commit with backup commands
• Trying git snapshot which is invalid

3. Given this sequence of commands:

echo "Hello" > file.txt
git add file.txt
git commit -m "First snapshot"
echo "World" >> file.txt
git add file.txt
git commit -m "Second snapshot"

What does the second commit snapshot contain?

medium

A. Only the line "World" added to file.txt

B. The entire file.txt with both "Hello" and "World" lines

C. Only the line "Hello" in file.txt

D. An empty file.txt

Solution

1. Step 1: Understand what each commit saves

   Each commit saves a full snapshot of the file at that time, not just changes.

2. Step 2: Analyze the second commit content

   After appending "World", the second commit snapshot includes both "Hello" and "World" lines in file.txt.

3. Final Answer:

   The entire file.txt with both "Hello" and "World" lines -> Option B

4. Quick Check:

   Git snapshots save full file content [OK]

Hint: Each commit saves full file content, not just added lines [OK]

Common Mistakes:

• Thinking commit saves only new lines
• Confusing snapshots with diffs
• Assuming commit saves partial file

4. You ran git commit but Git says "nothing to commit, working tree clean". What is the most likely reason?

medium

A. There are no changes since the last snapshot

B. You forgot to add files with git add before commit

C. Your Git repository is corrupted

D. You need to restart your computer

Solution

1. Step 1: Understand the message meaning

   "Nothing to commit, working tree clean" means no changes are detected compared to last commit.

2. Step 2: Check if files were changed

   If no files changed, Git has no new snapshot to save, so commit does nothing.

3. Final Answer:

   There are no changes since the last snapshot -> Option A

4. Quick Check:

   No changes = no new snapshot [OK]

Hint: No changes means no new commit possible [OK]

Common Mistakes:

• Assuming you must always run git add before commit even if no changes
• Thinking repository is corrupted
• Restarting computer unnecessarily

5. You want to save your project state but only some files changed. How does Git store this when you run git commit?

hard

A. Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally

B. Git saves only the changed files as diffs

C. Git saves only the changed files as full copies

D. Git saves nothing until you run git push

Solution

1. Step 1: Recall Git snapshot model

   Git saves a full snapshot of the project at commit time, not just diffs.

2. Step 2: Understand Git's storage optimization

   Internally, Git reuses unchanged files from previous commits to save space efficiently.

3. Final Answer:

   Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally -> Option A

4. Quick Check:

   Snapshots with internal reuse = Git saves a full snapshot of all files, but reuses unchanged files from previous commits internally [OK]

Hint: Git snapshots all files but stores unchanged ones efficiently [OK]

Common Mistakes:

• Thinking Git saves only diffs
• Believing commit saves nothing until push
• Assuming changed files are saved as full copies only