Why VCS exists : The pendrive problem

The problem arises when two or more developers are working on a single project. It is kind of ok for a single developer. For a single developer let’s say Ram writes a code and saves it. The only problem with single developer is that they can’t track the code that when they changed the code.

Later, he found that there was a bug in the code and asks his teammate Shyam to patch it. Ram saves it in a pendrive and gives the pendrive to Shyam. Shyam adds a lot of code and returns the pendrive. The first problem arises : There is no track of which part of the code was added. If there would have been that who added the code and when, this issue would have resolved.

Another problem : if both Ram and Shyam writes different code in the same project then code would be conflicted and then they are no longer working on the same project. And the code would get messy. So, to fix it, we will track who wrote the messy code and revert it back. Its also a nice tool for blaming the person who wrote messy code.

The ultimate source of truth should be made. Noone will ask that what code you have written or so. The pendrive here was the source of truth on which everyone relied upon. And for everyone to collab, we need a server, a platform.

In total, the pendrive problem is that you wont be able to track, basically who changed the code, when it was changed and what was changed.