Skip to main content

Why Version Control Exists: The Pen-drive Problem

Updated 2 min readMarkdown
Part of seriesAssignments

Let’s imagine we are building a app or website, so obviously the code base would be of a decent size.

One day while working on it, we suddenly bumped into an error which we couldn’t solve. So to solve the error, we took help from a friend named as X. To provide the friend with the source code, what we did is: we stored the entire source code inside a pen-drive, and gave it to our friend. After some time, our friend solved the error, and stored the fresh new fixed code inside the same pen-drive and gave it back. But now when we opened the source code, there was a new problem. The problem was not about a bug, but of unfamiliarity. The new source code provided by our friend seems new to us, as we didn’t know in which places the code had been changed and for what purpose. Here arises the problem of traceability.

Further, in later discussions our friend X told us that he was interested in the software we were building, so he want to contribute in it. So what we did is, we again provided the entire code base to him through the help of the same pen-drive. Here comes the twist, after some days, when we had a conference together, we noticed that while developing some features we both have edited some of our pre-existed code on our own different local PCs. And now, there exists two different versions of the same software which is a big issue.

To solve all these issues, a version control system was strongly needed which would help us in traceability, and there would a single version of the source code of an software. And this is where Git was developed.

Git is a version control system developed by Linus Torvalds as a side project to keep and manage the code base of his main project i.e. Linux OS.

Why Version Control Exists: The Pen Drive Problem - DEV Community

No comments yet. Be the first to comment.

More from this blog