# Why Version Control Exists: The Pendrive Problem

## The Software World Before Version Control

Before Git or any other Version Control System (VCS), the software development world was **chaotic.**  
There was no structured way to track changes, no collaboration history, and no safety net.

Developers relied on **pendrives, emails, and multiple folders** to share and manage codebases.

## How Developers Shared Code Back Then

In the absence of version control:

* Code was copied to **pendrives** and handed to teammates.
    
* Projects were sent as **ZIP files over email.**
    
* Multiple folders were created to represent different version.  
    
    ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1768646954554/1373cbcc-38af-455d-8c13-b2507ce8d1ed.png align="center")
    

```bash
project/
├── final/
├── final_v2/
├── final_v2_ui_fix/
├── latest_final/
├── latest_final_use_this/
```

A Real Example: Mukul Without Git

Let’s say **Mukul** is a frontend developer building a React UI — **without using any version control system**.

He wants to :

* Build UI components
    
* Test new layouts
    
* Improve code structure
    
* Fix bugs
    

Since Git doesn’t exist in this world, Mukul relies on:

* Creating **new folders** for every change.
    
* Using Notepad to saving the changes before some experimenting.
    
* Remembering changes in his head.
    

One folder might contain dashboard components , other contain some styling fix in it .  
Soon mukul realize no folder contain all the code of the project and it became annoying to handle the project.

## The Biggest Problem: No Change Tracking

There is no history of changes. if mukul break something he can’t compare versions of code and can’t even go back easily to previous changes.

Now, all this chaos happens just with one developer working alone. How will you handle when the team of 3 or 4 is working on the same project. No one have the actual updated code, everyone lags somewhere with the changes made by the other developer.

Manual methods like pendrives, emails, and folders **completely failed** when the team size is increasing or the codebase become complex.

## Why Version Control Became Mandatory

As software evolved, everything grew:

* Codebases became larger.
    
* Teams became distributed
    
* Release cycles became faster
    
* Mistakes became more expensive
    

At that scale, managing code with pendrives, emails, and “final” folders was no longer just inefficient — it was **dangerous**.

A world without version control is possible — but modern software isn’t.