# Why there is a need for Version Control?

![Why Version Control Exists: The Pendrive Problem - DEV Community](https://media2.dev.to/dynamic/image/width%3D800%2Cheight%3D%2Cfit%3Dscale-down%2Cgravity%3Dauto%2Cformat%3Dauto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvvpce1htpbfnw9f4duy1.png align="left")

## The Pendrive Era and its Problems

Before Git became the industry standard, moving code was a physical or manual task.Developers would finish a feature, zip up the folder, and either email it to a teammate or literally walk a pendrive across the office.You didn't have branches,you had folders eg. project\_v1,project\_v1\_final,project\_v1\_final\_v2,project\_v1\_FINAL\_FOR\_REAL\_FIXED

### The Problem

The pendrive wasn't just slow; it was dangerous for the codebase.The major problems were:

1. **The Overwrite Catastrophe:** Imagine Developer A and Developer B both copy the "latest" folder. They both spend 4 hours coding. Whoever copies their folder back to the pendrive *last* effectively deletes everything the first person did.
    
2. **The "Who Did This?" Mystery:** In a manual system, there is no audit trail. If a bug appears in production, you can't see who changed that specific line of code or *why* they changed it.
    
3. **Zero Concurrency:** Teams were forced to work in "linear" mode. "I can't touch the login page because Dave is currently editing it on his laptop."
    

### The Collaboration Problem

* **Scaling Issues:** A pendrive works for two friends in a dorm room. It does **not** work for 500 engineers at Google or Meta working on the same repository simultaneously.
    
* **The Mental Tax:** Developers spent 20% of their time just managing files instead of writing logic. Version control automates the "management" so humans can focus on the "creation."
    

## Why Version Control Became Mandatory

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1769870629932/e43dc686-cdab-47d7-9bd6-103cac5e7755.png align="center")

Version control systems solved all the pendrive-era problems at once:

1. Every change is tracked
    
2. Multiple people work in parallel
    
3. Conflicts are detected, not hidden
    
4. Full history is preserved
    
5. Rollback is always possible