Advanced Debugging Strategies: Finding and Fixing Bugs

Debugging is an essential skill. Every programmer spends more time debugging than coding. Professional techniques make it faster. Types of Bugs Syntax Errors: Code won't run name = "Arun # Missing closing quote Runtime Errors: Code crashes while running x = int("abc") # ValueError: invalid literal Logic Errors: Code runs but gives wrong results total = 0 for i in range(1, 5): total += 1 # Wrong! Should be total += i print(total) # Gives 4, not 10 Debugging Techniques 1. Print Debugging Simplest method: add print statements def calculate_grade(marks): print(f"Input marks: {marks}") # Debug print percentage = (marks / 500) * 100 print(f"Percentage: {percentage}") # Debug print if percentage >= 90: grade = "A+" elif percentage >= 80: grade = "A" else: grade = "B" print(f"Grade: {grade}") # Debug print return grade Result = calculate_grade(450) 2. Using Logging (Better than print) import logging logging.basicConfig(level=logging.DEBUG) logger = logging.getLogger(__name__) def calculate_grade(marks): logger.debug(f"Input marks: {marks}") percentage = (marks / 500) * 100 logger.debug(f"Percentage: {percentage}") if percentage >= 90: grade = "A+" elif percentage >= 80: grade = "A" else: grade = "B" logger.info(f"Student got grade: {grade}") return grade Logging levels: DEBUG - Detailed info for debugging INFO - General information WARNING - Warning messages ERROR - Error messages CRITICAL - Critical issues 3. Using Try-Except def get_student_marks(): try: marks = int(input("Enter marks: ")) if marks < 0 or marks > 500: raise ValueError("Marks must be 0-500") return marks except ValueError as e: print(f"Error: {e}") return None 4. Assertions Assertions check if conditions are true. Helpful during development. def calculate_percentage(marks, total=500): assert marks >= 0, "Marks cannot be negative" assert marks <= total, "Marks cannot exceed total" assert total > 0, "Total must be positive" percentage = (marks / total) * 100 return percentage print(calculate_percentage(450)) # Works print(calculate_percentage(-50)) # AssertionError: Marks cannot be negative 5. Using Debugger (pdb) import pdb def find_average(numbers): pdb.set_trace() # Execution pauses here total = sum(numbers) average = total / len(numbers) return average result = find_average([10, 20, 30]) print(result) When execution pauses, you can: l (list) - Show code n (next) - Execute next line s (step) - Step into function c (continue) - Continue execution p variable - Print variable value q (quit) - Quit debugger 6. Systematic Debugging Approach Step 1: Reproduce the bug - What exact input causes it? - When does it happen? - Can you create a minimal example? Step 2: Understand the bug - What's the expected output? - What's the actual output? - Where is the difference? Step 3: Form a hypothesis - What might be causing it? - Test your hypothesis Step 4: Fix it - Change one thing - Test if fixed - If not, try next hypothesis Practical Example: Buggy Grade Calculator def calculate_class_average(students_marks): total = 0 for marks in students_marks: total = marks # BUG! Should be total += marks average = total / len(students_marks) return average test_data = [450, 480, 470] result = calculate_class_average(test_data) print(f"Average: {result}") # Wrong result! Debug approach: import logging logging.basicConfig(level=logging.DEBUG) logger = logging.getLogger(__name__) def calculate_class_average(students_marks): total = 0 for marks in students_marks: logger.debug(f"Processing marks: {marks}, current total: {total}") total += marks # Fixed! logger.debug(f"Final total: {total}") average = total / len(students_marks) logger.info(f"Average calculated: {average}") return average test_data = [450, 480, 470] result = calculate_class_average(test_data) print(f"Average: {result}") # Correct! 7. Testing to Prevent Bugs def test_calculate_percentage(): assert calculate_percentage(450, 500) == 90, "90% test failed" assert calculate_percentage(500, 500) == 100, "100% test failed" assert calculate_percentage(0, 500) == 0, "0% test failed" print("All tests passed!") test_calculate_percentage() Common Bugs in Python 1. Off-by-one errors for i in range(len(list)): # Correct for i in range(len(list) + 1): # Bug! Index out of range 2. Mutable default arguments def add_student(name, subjects=[]): # Bug! subjects.append(name) return subjects # Correct def add_student(name, subjects=None): if subjects is None: subjects = [] subjects.append(name) return subjects 3. Not handling None marks = None percentage = (marks / 500) * 100 # TypeError! # Better if marks is not None: percentage = (marks / 500) * 100 4. Incorrect comparison if student_name = "Arun": # Bug! = is assignment if student_name == "Arun": # Correct Debugging Checklist ☐ Can you reproduce the bug consistently? ☐ Have you printed/logged all variables? ☐ Have you checked boundary conditions? ☐ Have you read error messages carefully? ☐ Have you searched similar issues online? ☐ Have you tested with simpler input? ☐ Have you stepped through with a debugger? Practice: Take a buggy Python program and debug it using multiple techniques. Write tests to prevent regressions.

---

Under the Hood: Advanced Debugging Strategies: Finding and Fixing Bugs

Here is what separates someone who merely USES technology from someone who UNDERSTANDS it: knowing what happens behind the screen. When you tap "Send" on a WhatsApp message, do you know what journey that message takes? When you search something on Google, do you know how it finds the answer among billions of web pages in less than a second? When UPI processes a payment, what makes sure the money goes to the right person?

Understanding Advanced Debugging Strategies: Finding and Fixing Bugs gives you the ability to answer these questions. More importantly, it gives you the foundation to BUILD things, not just use things other people built. India's tech industry employs over 5 million people, and companies like Infosys, TCS, Wipro, and thousands of startups are all built on the concepts we are about to explore.

This is not just theory for exams. This is how the real world works. Let us get into it.

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: Advanced Debugging Strategies: Finding and Fixing Bugs at Scale

Understanding advanced debugging strategies: finding and fixing bugs 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 advanced debugging strategies: finding and fixing bugs 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 • Programming & Coding • Aligned with NEP 2020 & CBSE Curriculum