1.4. Reflection Checkpoint

Key Takeaways

• Version control gives every change a timestamped, attributable, reversible record — value that exists even for a single developer working alone, not just for teams.
• Git is the local version control engine; GitHub is a cloud hosting platform built around Git that adds collaboration and workflow tools on top. Most Git operations need no internet connection at all.
• A repository is the tracked container for a project's full history; a commit is a local snapshot of that history; a branch is a lightweight, movable pointer that lets you build a separate line of history without disturbing others.
• Nothing is shared with collaborators until you push — commits and branch changes are invisible on GitHub until that point.

Connecting Forward

Phase 2 puts these building blocks to work inside GitHub specifically: how accounts, organizations, and Enterprise tiers are structured, how the GitHub Flow turns "branch, commit, pull request" into a repeatable team workflow, and how Markdown and GitHub's own clients (Desktop and Mobile) fit around that flow.

Self-Check Questions

• Without looking back at 1.2, could you explain to a non-technical coworker why "Git" and "GitHub" aren't interchangeable words?
• Why does Git's local-first design (commits and branches as purely local actions) make it safer to experiment with your code, rather than riskier?