Why git exists
What this lesson covers
Section titled “What this lesson covers”L1 builds the mental model that the rest of T7 depends on. It does not teach any git commands. It teaches the conceptual frame that makes commands sensible when they appear in L2.
The two load-bearing ideas:
-
Version control is a record of changes over time, not just storage of the current state. That record is itself useful and is what version control adds over folder backups or thumb drive copies.
-
Git stores snapshots of project state over time. This is the mental model that makes every later command (commit, checkout, branch, merge) coherent.
By the end of L1, the reader will be able to
Section titled “By the end of L1, the reader will be able to”- State the problem version control solves and why ad-hoc approaches (file naming conventions, manual backups, copy-and-paste) fail at scale
- Describe the snapshot mental model that underpins how git records project history
- Explain the difference between centralized and distributed version control with one concrete reason each matters
- Identify three signs that a project needs version control beyond what folder backups provide
- Articulate what skills the rest of Phase 1 builds on this foundation
Prerequisites
Section titled “Prerequisites”- Comfort with the idea of files and folders on a computer
- No prior git knowledge required
- No programming experience required for L1 specifically (L2 onward will assume some command-line comfort)
Reading map for the four named audiences
Section titled “Reading map for the four named audiences”This track is written for new developers, existing developers, development managers, and technical product managers. L1 is the single lesson where all four read the same content in roughly equal depth. From L2 onward, experienced developers will skim WHY sections and focus on HOW; managers and product managers will find Phase 3 most directly useful. L1 establishes the shared vocabulary.
What this lesson deliberately does not cover
Section titled “What this lesson deliberately does not cover”- Any git commands (deferred to L2)
- Repository structure or filesystem layout (deferred to L2)
- The staging area mental model (deferred to L2)
- Commit messages (deferred to L3)
- Recovery patterns (deferred to L4)
If you find yourself wanting to know “what command do I type to do that,” the answer is in L2. L1 is intentionally command-free so the mental model lands without command-syntax distraction.
Estimated reading time
Section titled “Estimated reading time”12 to 15 minutes for reading; 5 to 10 minutes for the practice section. Total time investment for L1 including reflection: about 25 minutes.