Version control concept (Git) in Intro to Computing - Real World Applications

Real World Mode - Version control concept (Git)

Version Control as a Library of Drafts

Imagine you are writing a big book. Instead of writing on one single paper, you keep many drafts in a special library. Each draft is a snapshot of your book at a certain time. You can look back at any draft, see what changed, or even bring back an old draft if you want. This library helps you keep track of all your changes without losing anything.

Version control with Git works like this library. It stores snapshots of your project files over time. You can go back to any snapshot, compare changes, or share your drafts with friends who are also writing the book.

Mapping Version Control Concepts to the Library Analogy

Computing Concept	Real-World Equivalent	Description
Repository (Repo)	Library of drafts	A place where all versions (drafts) of the book are stored safely.
Commit	Saving a new draft	A snapshot of the book at a certain moment, capturing all changes made so far.
Branch	Separate writing path or storyline	A different version of the book where you can try new ideas without changing the main story.
Merge	Combining two storylines	Bringing changes from one draft or storyline into another to unify the work.
Clone	Copying the library	Making your own full copy of the library to work on the drafts independently.
Push	Sending your draft to the shared library	Uploading your saved draft so others can see and use it.
Pull	Getting the latest drafts from the library	Downloading updates made by others to keep your copy current.

A Day in the Life of a Writer Using the Library

Imagine you start your day by opening your copy of the library. You pick up the latest draft of your book and start writing a new chapter. After finishing, you save this as a new draft (commit) so you don't lose your work.

Later, your friend wants to add a new subplot. They create their own branch, a separate storyline, and write their part without changing your main draft. When they finish, they merge their subplot back into the main story, combining both ideas.

You both push your drafts to the shared library so everyone can see the latest versions. Before starting the next day, you pull the newest drafts to make sure you have all the updates.

Where the Library Analogy Breaks Down

• The analogy simplifies complex Git features like conflict resolution during merges, which in real life can be tricky and require careful editing.
• In the analogy, drafts are physical papers, but Git stores data digitally and efficiently using snapshots and differences.
• The library suggests a central place, but Git can work fully distributed, meaning everyone has a complete copy, unlike a single physical library.
• Some Git commands and workflows (like rebasing) don't have a simple equivalent in the library analogy.

Self-Check Question

In our library analogy, what would creating a new branch be equivalent to?

Answer: Starting a separate writing path or storyline to try new ideas without changing the main draft.

Key Result

Version control with Git is like a library of drafts where each saved draft is a snapshot of your book at a moment in time.