Git from Zero to Hero — Part 1: What is Version Control? (Source Control Explained)

What is Source Control?

When we write code or even a simple document, we often try to protect our work by creating copies.

For example:

Imagine you are writing a thesis.
You save your file as:

thesis.doc

Then you think: “What if something goes wrong?”

So you create a copy:

thesis_copy.doc

Later, you make more changes and create another version:

thesis_final.doc
thesis_final_v2.doc
thesis_final_real_final.doc 😄

After some time, you have many files, and it becomes hard to manage them.

The Problem

• Which version is the latest?

• Where was that paragraph I deleted?

• What did I change yesterday?

Now imagine this in a software project:

• Version 2.6 is already released

• You are working on version 2.7

• You keep copying folders again and again

This becomes messy very quickly.

The Solution: Source Control

Source Control (or Version Control) solves this problem.

It helps you:

• Track changes over time

• Save history automatically

• Restore old versions

• Understand what changed and when

Working in a Team

In a team, things get even more complex:

• Multiple people work on the same file

• Changes may conflict

• Bugs need to be tracked

With tools like Git:

• You can see who made a change

• When the change was made

• What exactly was modified

You can also:

• Merge changes from different people

• Track issues (e.g., “#420 bug fixed”)

• Understand the full history of a project

Final Thought

Source Control is not just a tool.
It is a way of working.

And one of the most powerful tools for this is:

Git

>>> Next: Understanding Diff (What Changed?)