Version Control Explained : A Solution to the Pen drive Problem
(For the Gen-z's who i don’t think have any idea what "final_updated_latest.zip" means)
An enthusiast who wants to learn new things and try to pass on the same through articles on those topics in simple words.
Have you ever shared code using a Pen drive, Email, Whatsapp or any such means?
Or do you still save your folders with names project_folder, project_folder_main ,project_folder_main_final ?
DID YOU JUST SAY YES?
WHAT?
Even today?
I suppose, then, you are in dire need to know about Version Control and Git.
So lets dive into this world and reduce the TRAUMA which we all have been facing.
What exactly is Version Control?
In simplest of words if i have to define Version Control, “it is the practice of tracking and managing changes to software code that you write”.
Now, some of you might be beginners like me and would be thinking “how hard can it be to manage code?”. The projects hardly are 200 or may be 300 or at max 500 lines of code. But that’s where our thinking is a little like what we call “Kuen ka mendhak”.
Ok, lets try and understand it with an analogy.
Imagine you are standing on ground floor next to a skyscraper 50 stories tall and and someone asks you to memorise whatever you can see within your visible sight range. It would be easy right? Now, that same person then asks you climb five floors and carry out the same exercise and then again next five and next, till you reach the fiftieth floor.
Now, can you understand the problem? We, the beginners are on the ground floor standing next to that building and the code which we write is like the limited visibility range. And, when we keep gaining experience our own code keeps growing. The fiftieth floor view is like a giant company with thousands, even may be millions of lines of code and hundreds and thousands of coders working simultaneously on that. Also, so many new people join and so many leave and go to some other. How in the world, do you think is that code base is being managed? Who is coding what? Who is changing what? What was the change that brought the entire website down by introducing a bug? How to get back to the last stable version of the website or the program till the team irons out the bug? Where is that version?
Why Version Control Exists
Can visualise the chaos?
To the rescue comes version control. To cut down on this chaos, to make life easier of a coder.
Version control was not invented because developers love tools.
It was invented because developers were suffering.
Before Git, before GitHub, before fancy CI/CD words entered our lives, there was a darker time. A simpler time. A time ruled by:
Pen drives
Emails
Folders named
final,final_v2,final_latest_really_final
Version control exists because humans make mistakes, and software development multiplies those mistakes as the team size or the company size grows.
The Pen drive problem in Software Development
Let’s rewind to a very real scenario.
You’re working on a project with 3 friends.
One pen drive.
One project.
Zero process.
Day 1
You copy the project to a pen drive.
Life is good.
Day 3
Two people modify the same file.
Both think their version is correct.
Day 5
Someone overwrites the pen drive.
No backup.
No history.
No mercy.
This is not fiction.
This is how software was written.
The pen drive became:
The database
The server
The source of truth
The single point of failure
One drop. One overwrite. One mistake.
Everything gone.
Problems Faced Before Version Control Systems
1. The “Final” Folder Disaster
Every developer had folders like:
project/
├── final/
├── final_v2/
├── final_v3_fixed/
├── final_latest/
├── final_latest_use_this_one/
No one knew:
Which version worked
Who changed what
Why it broke
The folder names were emotional, not logical.
2. Overwriting Code Without Knowing
Two developers edited the same file.
One copied their version.
The other pasted theirs.
One person won.
The other’s work disappeared.
No warning.
No conflict.
No apology.
Just silence.
3. No History, No Accountability
Someone asked:
“Who broke the build?”
Everyone replied:
“Not me.”
Because there was no record:
No timeline
No author
No change history
The pen drive didn’t care about responsibility.
4. Collaboration Was Pure Chaos
Emailing code:
project_updated.zipproject_updated_fixed.zip
Teamwork became a guessing game.
Real-World Team Problems
As teams grew, this model collapsed.
You could not build:
Startups
Large systems
Production software
…using pen drive logic.
Why Version Control Became Mandatory
Version control didn’t just help software development.
It saved it.
It solved the pen drive problem by introducing:
A central source of truth
Complete change history
Safe collaboration
Parallel development
Easy rollback
Now instead of saying:
“I think this was working yesterday”
You can say:
“Let’s go back to that version.”
Confidence replaced fear.
Pen drive Workflow vs Version Control Workflow
❌ Pendrive-Based Workflow
Developer A → Pendrive → Developer B
↓
Overwrite / Confusion
✅ Version Control Workflow
Developer A → Repository ← Developer B
↑ ↓
History Collaboration
Same people.
Same code.
Very different outcomes.
Final Thoughts
Version control exists because developers needed:
Safety
Structure
Sanity
It turned software development from survival mode into engineering discipline.
So the next time you run git commit, remember:
This command exists because someone, somewhere, lost their entire project to a pendrive.
And the folder was named
final_project_latest.
Oh oh, before i sign off….
Don’t fret over what git commit means.
There’s more to come on that.
Signing off,
(Only until the next gyan i can absorb for giving back here…)
To Learn what is GIT and its basics :
https://my-journey-into-the-unknown.hashnode.dev/git-for-beginners-whatwhyhow-of-it?t=1768587820535
If you found this article helpful, share it with others and feel free to leave your feedback—I’d love to hear your thoughts!
