<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Why Version Control Exists]]></title><description><![CDATA[Why Version Control Exists]]></description><link>https://vcs-existance.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 11 Sep 2026 16:23:13 GMT</lastBuildDate><atom:link href="https://vcs-existance.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why Version Control Exists: The Pendrive Problem!]]></title><description><![CDATA[Introduction
As a good learner, it's important to understand why the topics we study matter, right? If we don't know the "WHY," we end up just memorizing concepts. So, I asked my professors why we need Git and whether the world wouldn't function smoo...]]></description><link>https://vcs-existance.hashnode.dev/why-version-control-exists-the-pendrive-problem</link><guid isPermaLink="true">https://vcs-existance.hashnode.dev/why-version-control-exists-the-pendrive-problem</guid><category><![CDATA[Git]]></category><category><![CDATA[GitHub]]></category><category><![CDATA[MERN Stack]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[software development]]></category><category><![CDATA[version control]]></category><dc:creator><![CDATA[Mohd Asif]]></dc:creator><pubDate>Sat, 17 Jan 2026 14:17:05 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1768658524419/9e6f662b-1be9-4ed9-a6d7-00e8d4b81b51.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h2 id="heading-introduction"><strong>Introduction</strong></h2>
<p>As a good learner, it's important to understand why the topics we study matter, right? If we don't know the "WHY," we end up just <strong>memorizing</strong> concepts. So, I asked my professors why we need Git and whether the world wouldn't function smoothly without it.</p>
<p>First, let's discuss why we need Git and how the world changed after its introduction!</p>
<h2 id="heading-whats-the-pendrive-era"><strong>What’s the pendrive Era?</strong></h2>
<p>Let’s start with a short story, which helps us to understand the concept of git.</p>
<p>As a developer working on a project, you are initially able to add features and make code adjustments. However, as your project grows, you need a variety of features to scale up and differentiate your product, so you enlisted the assistance of your knowledgeable friend who is highly skilled in that area.</p>
<p>But how does your friend add changes to your code??</p>
<ul>
<li><p>Either he has to be present at your place to make changes.</p>
</li>
<li><p>Or you have to store your code on a Pendrive and pass it to your friend, and he’ll apply changes and return the pendrive to you.</p>
</li>
</ul>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1768658249678/d6b05c4b-bc6f-4e93-a8a8-f22803921210.webp" alt class="image--center mx-auto" /></p>
<p><strong>Problem: No Tracking -</strong> What changes were made, when they were made, and by whom cannot be tracked. There is no dependable mechanism to go back to a previous functional version if something breaks.</p>
<p><strong>Problem: No Collaboration -</strong> Several developers can’t collaborate effectively on a single project. Manual code sharing (USB, zip files, etc.) causes version confusion, overwrites, and conflicts.</p>
<p><strong>Problem: Work Lost -</strong> Multiple developers updating the same files frequently overwrite each other's changes in the absence of an effective version control system. This results in lost work, malfunctioning features, and an unreliable method of recovering earlier iterations.</p>
<p><strong>Problem: Conflicts and Confusion -</strong> Sharing code via USB, email, or zip files creates many copies without history, leaving developers unsure which version is latest, which changes are correct, and how to merge updates safely.</p>
<h2 id="heading-why-has-version-control-system-become-mandatory"><strong>Why has Version Control System Become Mandatory</strong></h2>
<p>A version control system tracks file changes over time, lets you view or restore older versions, and helps multiple developers work on the same project without overwriting each other’s work.</p>
<p><strong>GIT</strong> is one of the most popular Version Control System among developers.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1768658868279/c0b34375-bec5-464e-b598-848beb026619.webp" alt class="image--center mx-auto" /></p>
<p>Therefore, a version control system tracks every change made to files over time.</p>
<h3 id="heading-the-solution-enter-the-chaicode-tracker-cct"><strong>The Solution: Enter the "ChaiCode Tracker" (CCT)</strong></h3>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1768659224102/9298e000-0ae7-430c-a976-66d9d301dfc1.webp" alt class="image--center mx-auto" /></p>
<p>To solve the mess of pendrives and ZIP files, we need a system that doesn't just "save files" but actually <strong>tracks progress</strong>. In our world, let’s call this system the <strong>ChaiCode Tracker (CCT)</strong>.</p>
<p>To understand how professional developers work, you need to know that this "Tracker" is split into two parts:</p>
<h4 id="heading-1-git-your-personal-progress-tracker"><strong>1. Git: Your Personal Progress Tracker</strong></h4>
<p>Think of <strong>Git</strong> as the actual <strong>ChaiCode Tracker (CCT)</strong> software that lives on your computer.</p>
<ul>
<li><p>It watches every line of code you write.</p>
</li>
<li><p>It remembers every version of your project locally, so you don't need to make "final_v2" folders.</p>
</li>
<li><p>It was created by <strong>Linus Torvalds</strong> to track the progress of Linux.</p>
</li>
</ul>
<h4 id="heading-2-github-the-central-meeting-point"><strong>2. GitHub: The Central Meeting Point</strong></h4>
<p>While Git tracks your work locally, you still need a way to share that work with your team without using a pendrive. This is where <strong>GitHub</strong> comes in.</p>
<ul>
<li><p><strong>GitHub</strong> is the <strong>ChaiCode Tracker Server</strong>—a central hub on the cloud where everyone connects.</p>
</li>
<li><p>It acts as the <strong>"Single Source of Truth"</strong>.</p>
</li>
<li><p>If one finishes a feature, he sends it to GitHub; if Hitesh fixes a bug, he sends it to GitHub.</p>
</li>
</ul>
<p>Instead of passing physical disks, everyone simply "syncs" their work with this central server. The pendrive is officially dead!</p>
<h2 id="heading-the-story-behind-git"><strong>The Story behind GIT</strong></h2>
<p>Git was created to solve a real problem in the Linux community. Earlier, Linux developers used a tool called BitKeeper to manage code. It worked well, but it was not open source, which made developers uncomfortable. When conflicts arose, the free license was removed, and many developers suddenly lost access.</p>
<p>This created a serious challenge: how to manage a huge open-source project without a reliable tool. To avoid depending on another company, Linux creator Linus Torvalds decided to build a new system himself. He designed Git to be fast, secure, distributed, able to handle large projects, and completely open source. Git was quickly adopted and is now widely used.</p>
]]></content:encoded></item></channel></rss>