# Why Version Control Exists: The Pendrive Problem

Before tools like Git existed, developers commonly shared code using **pendrives, emails, or zip files**. This led to a classic set of problems—often called the *Pendrive Problem*.

### The Pendrive Problem

Imagine this situation:

* You copy your project to a pendrive and give it to a teammate.
    
* While they’re making changes, you also modify the same project.
    
* Later, the pendrive comes back with *their* version.
    
* Now you have:
    
    * `project_final`
        
    * `project_final_latest`
        
    * `project_final_latest_v2`
        

This creates **confusion, conflicts, and wasted time**.

### Problems Without Version Control

* No history of changes
    
* Can’t track who changed what and why
    
* Easy to lose working code
    
* Hard to collaborate with multiple people
    
* No safe way to experiment (fear of breaking code)
    

### How Version Control Solves This

Version control systems (like **Git**) were created to fix exactly these issues:

* ✅ **Complete history** of every change
    
* ✅ **Multiple people** can work on the same project safely
    
* ✅ **Branching** allows experimentation without risk
    
* ✅ **Easy rollback** to any previous working version
    
* ✅ **Central source of truth** (GitHub, GitLab, Bitbucket)
    

### In One Line

**Version control exists because sharing code via pendrives and files was chaotic, unsafe, and unscalable—especially for teams.**