Why Version Control Exists: The Pendrive Problem

Nowdays git and GitHub are very common. Anybody can imagine a developer's life before git and GitHub. How did they control the application version? How can multiple developers work on the same project at the same time? This was very difficult to work with but now we have git and github very helpful for developers.
Why Version Control Exists
Biggest headache in software development.
Where is the latest version of my file?
Where are the changes I made yesterday?
How do I get the old version of my code?
And the biggest question is who broke the code?
Pendrive Analogy in Software Development (Real Story)
I developed a project and copy in a pendrive and gave it to another developer. They update the code, add functionlity and a pendrive gives me back, and then start real drama.
Pendrive work fellow

project_final/project_final_v2/project_latest_final/project_latest_final_updated/project_final_real/project_final_real_last/
Here are all the file names and code meshop, nobody has any idea which is the real and updated file. There are actual real team problems when 5 developers are working on the same project, backend changes, frontend changes, bug fixing, how can track changes and code all the developers working diffrent diffrent folder then the whole proejct in out of control.
What Problems Did Version Control Solve?
Version control (Git) promised:
Every change will be tracked
Every update will be recorded
Who did it, when they did it, and why they did it โ all the information will be available
If something breaks, you can revert to an older version
Multiple people can work on the same project safely
In short: Version Control = Team's time machine + security camera + backup system ๐โ




