Version Control with Git: How Professional Developers Work

Version Control with Git: How Professional Developers Work

Imagine working on a school project with friends. You email versions: "Project_v1.docx", "Project_v2.docx", "Project_v2_final.docx", "Project_v2_final_REALLY_FINAL.docx". It's chaos. You don't know who changed what, you can't revert mistakes, merging edits is a nightmare.

Version control is the solution. It's like a time machine for your code—you can go back to any previous version, see who made what changes, and merge work from multiple developers cleanly.

Why Version Control Matters

Scenario without version control:

• Alice writes feature A, sends file to Bob
• Bob adds feature B, sends back to Alice
• Alice adds feature C but accidentally deletes feature B
• Now feature B is lost forever

Scenario with Git:

• Alice creates a branch, adds feature A, commits with message "Add login feature"
• Bob creates a separate branch, adds feature B, commits with message "Add signup feature"
• Both push to GitHub. Git automatically merges features (usually without conflict)
• If conflict, Git marks it clearly so they can resolve together
• If Alice makes a mistake, git log shows exactly what changed and we can revert

Git Basics: The Core Commands

1. Initialize a Repository

# Create a new folder for your project
mkdir my_ai_project
cd my_ai_project

# Initialize git
git init

# This creates a hidden .git folder that tracks changes

2. Make Changes and Commit

# Create a file
echo "print('Hello, AI!')" > main.py

# Check status (what changed?)
git status
# Output: Untracked files: main.py

# Stage the file (prepare to save)
git add main.py

# Or stage all changes
git add .

# Check status again
git status
# Output: Changes to be committed: main.py

# Commit (save with message)
git commit -m "Add main.py with hello message"

# View commit history
git log
# Output:
# commit a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6
# Author: Raj 
# Date: Feb 10 2024
# Add main.py with hello message

3. Branching: Work in Parallel

# Create a new branch (parallel version)
git branch add-database

# Switch to the new branch
git checkout add-database
# Or in newer Git versions:
# git switch add-database

# Now you're on the "add-database" branch
# Changes here don't affect the main branch

# Make changes
echo "database_connection = True" >> main.py
git add .
git commit -m "Add database connection logic"

# Switch back to main branch
git checkout main

# The database changes are NOT in main branch
# main branch still has original code

# Switch back to add-database
git checkout add-database
# Now the database changes are here

# When feature is ready, merge back to main
git checkout main
git merge add-database

# Now main has both: original code + database feature

Merge Conflicts: When Parallel Paths Collide

# Scenario: Two people edit the same line

# Person A (main branch):
# Changed line 5 from "x = 5" to "x = 10"

# Person B (feature branch):
# Changed line 5 from "x = 5" to "x = 15"

# When merging:
git merge feature-branch

# Git finds conflict:
# <<<<<<< HEAD
# x = 10  (from main)
# =======
# x = 15  (from feature-branch)
# >>>>>>> feature-branch

# You must manually choose:
# Keep x = 10? Keep x = 15? Keep both?

# After resolving:
git add .
git commit -m "Merge feature-branch, resolved conflict on line 5"

Remote Repositories: GitHub, GitLab

A remote is a copy of your repository in the cloud (like backup in cloud storage).

# Set up a GitHub repository (create on GitHub.com first)

# Add remote (connect local git to GitHub)
git remote add origin https://github.com/yourname/my_ai_project.git

# Push local commits to GitHub
git push -u origin main

# Later, to update:
git push  # Uploads local commits to GitHub

# If someone else pushed changes:
git pull  # Downloads updates from GitHub

# Clone someone else's project
git clone https://github.com/someoneelse/their_project.git

Real-World Development Workflow

A developer's typical day at a company:

1. Morning: Pull latest code from GitHub

   
   git pull origin main
   

2. Create Feature Branch: Work on a new feature

   
   git checkout -b add-user-authentication
   

3. Throughout Day: Make commits as you progress

   
   # Morning: Basic structure
   git commit -m "Create User class with login method"
   
   # Mid-day: Add password hashing
   git commit -m "Add bcrypt password hashing for security"
   
   # Afternoon: Add email verification
   git commit -m "Add email verification for new accounts"
   

4. Evening: Push branch to GitHub and create Pull Request

   
   git push origin add-user-authentication
   

   On GitHub website: Click "Create Pull Request"

5. Next Day: Code review by teammates, feedback, improvements
   • Teammate: "Good work! Can you add unit tests?"
   • You: Make changes, commit, push again (auto-updates PR)
6. Approval: Senior developer approves, merges to main

   
   # Senior dev clicks "Merge" on GitHub
   # Your changes are now in production
   

Best Practices

Git is the tool that connects individual programmers into cohesive teams building complex software. Master Git, and you're speaking the language of professional development.

From Concept to Reality: Version Control with Git: How Professional Developers Work

In the professional world, the difference between a good engineer and a great one often comes down to understanding fundamentals deeply. Anyone can copy code from Stack Overflow. But when that code breaks at 2 AM and your application is down — affecting millions of users — only someone who truly understands the underlying concepts can diagnose and fix the problem.

Version Control with Git: How Professional Developers Work is one of those fundamentals. Whether you end up working at Google, building your own startup, or applying CS to solve problems in agriculture, healthcare, or education, these concepts will be the foundation everything else is built on. Indian engineers are known globally for their strong fundamentals — this is why companies worldwide recruit from IITs, NITs, IIIT Hyderabad, and BITS Pilani. Let us make sure you have that same strong foundation.

Object-Oriented Programming: Modelling the Real World

OOP lets you model real-world entities as code "objects." Each object has properties (data) and methods (behaviour). Here is a practical example:

class BankAccount:
    """A simple bank account — like what SBI or HDFC uses internally"""

    def __init__(self, holder_name, initial_balance=0):
        self.holder = holder_name
        self.balance = initial_balance    # Private in practice
        self.transactions = []            # History log

    def deposit(self, amount):
        if amount <= 0:
            raise ValueError("Deposit must be positive")
        self.balance += amount
        self.transactions.append(f"+₹{amount}")
        return self.balance

    def withdraw(self, amount):
        if amount > self.balance:
            raise ValueError("Insufficient funds!")
        self.balance -= amount
        self.transactions.append(f"-₹{amount}")
        return self.balance

    def statement(self):
        print(f"
--- Account Statement: {self.holder} ---")
        for t in self.transactions:
            print(f"  {t}")
        print(f"  Balance: ₹{self.balance}")

# Usage
acc = BankAccount("Rahul Sharma", 5000)
acc.deposit(15000)      # Salary credited
acc.withdraw(2000)      # UPI payment to Swiggy
acc.withdraw(500)       # Metro card recharge
acc.statement()

This is encapsulation — bundling data and behaviour together. The user of BankAccount does not need to know HOW deposit works internally; they just call it. Inheritance lets you extend this: a SavingsAccount could inherit from BankAccount and add interest calculation. Polymorphism means different account types can respond to the same .withdraw() method differently (savings accounts might check minimum balance, current accounts might allow overdraft).

Real-World System Design: Swiggy's Architecture

When you order food on Swiggy, here is what happens behind the scenes in about 2 seconds: your location is geocoded (algorithms), nearby restaurants are queried from a spatial index (data structures), menu prices are pulled from a database (SQL), delivery time is estimated using ML models trained on historical data (AI), the order is placed in a distributed message queue (Kafka), a delivery partner is assigned using a matching algorithm (optimization), and real-time tracking begins using WebSocket connections (networking). EVERY concept in your CS curriculum is being used simultaneously to deliver your biryani.

How the Web Request Cycle Works

Every time you visit a website, a precise sequence of events occurs. Here is the flow:

    You (Browser)          DNS Server          Web Server
        |                      |                    |
        |---[1] bharath.ai --->|                    |
        |                      |                    |
        |<--[2] IP: 76.76.21.9|                    |
        |                      |                    |
        |---[3] GET /index.html ----------------->  |
        |                      |                    |
        |                      |    [4] Server finds file,
        |                      |        runs server code,
        |                      |        prepares response
        |                      |                    |
        |<---[5] HTTP 200 OK + HTML + CSS + JS --- |
        |                      |                    |
   [6] Browser parses HTML                          |
       Loads CSS (styling)                          |
       Executes JS (interactivity)                  |
       Renders final page                           |

Step 1-2 is DNS resolution — converting a human-readable domain name to a machine-readable IP address. Step 3 is the HTTP request. Step 4 is server-side processing (this is where frameworks like Node.js, Django, or Flask operate). Step 5 is the HTTP response. Step 6 is client-side rendering (this is where React, Angular, or Vue operate).

In a real-world scenario, this cycle also involves CDNs (Content Delivery Networks), load balancers, caching layers, and potentially microservices. Indian companies like Jio use this exact architecture to serve 400+ million subscribers.

Production Engineering: Version Control with Git: How Professional Developers Work at Scale

Understanding version control with git: how professional developers work at an academic level is necessary but not sufficient. Let us examine how these concepts manifest in production environments where failure has real consequences.

Consider India's UPI system processing 10+ billion transactions monthly. The architecture must guarantee: atomicity (a transfer either completes fully or not at all — no half-transfers), consistency (balances always add up correctly across all banks), isolation (concurrent transactions on the same account do not interfere), and durability (once confirmed, a transaction survives any failure). These are the ACID properties, and violating any one of them in a payment system would cause financial chaos for millions of people.

At scale, you also face the thundering herd problem: what happens when a million users check their exam results at the same time? (CBSE result day, anyone?) Without rate limiting, connection pooling, caching, and graceful degradation, the system crashes. Good engineering means designing for the worst case while optimising for the common case. Companies like NPCI (the organisation behind UPI) invest heavily in load testing — simulating peak traffic to identify bottlenecks before they affect real users.

Monitoring and observability become critical at scale. You need metrics (how many requests per second? what is the 99th percentile latency?), logs (what happened when something went wrong?), and traces (how did a single request flow through 15 different microservices?). Tools like Prometheus, Grafana, ELK Stack, and Jaeger are standard in Indian tech companies. When Hotstar streams IPL to 50 million concurrent users, their engineering team watches these dashboards in real-time, ready to intervene if any metric goes anomalous.

The career implications are clear: engineers who understand both the theory (from chapters like this one) AND the practice (from building real systems) command the highest salaries and most interesting roles. India's top engineering talent earns ₹50-100+ LPA at companies like Google, Microsoft, and Goldman Sachs, or builds their own startups. The foundation starts here.

Key Vocabulary

Here are important terms from this chapter that you should know:

💡 Interview-Style Problem

Here is a problem that frequently appears in technical interviews at companies like Google, Amazon, and Flipkart: "Design a URL shortener like bit.ly. How would you generate unique short codes? How would you handle millions of redirects per second? What database would you use and why? How would you track click analytics?"

Think about: hash functions for generating short codes, read-heavy workload (99% redirects, 1% creates) suggesting caching, database choice (Redis for cache, PostgreSQL for persistence), and horizontal scaling with consistent hashing. Try sketching the system architecture on paper before looking up solutions. The ability to think through system design problems is the single most valuable skill for senior engineering roles.

Where This Takes You

The knowledge you have gained about version control with git: how professional developers work is directly applicable to: competitive programming (Codeforces, CodeChef — India has the 2nd largest competitive programming community globally), open-source contribution (India is the 2nd largest contributor on GitHub), placement preparation (these concepts form 60% of technical interview questions), and building real products (every startup needs engineers who understand these fundamentals).

India's tech ecosystem offers incredible opportunities. Freshers at top companies earn ₹15-50 LPA; experienced engineers at FAANG companies in India earn ₹50-1 Cr+. But more importantly, the problems being solved in India — digital payments for 1.4 billion people, healthcare AI for rural areas, agricultural tech for 150 million farmers — are some of the most impactful engineering challenges in the world. The fundamentals you are building will be the tools you use to tackle them.

Crafted for Class 7–9 • Software Development Tools • Aligned with NEP 2020 & CBSE Curriculum