AI Computer Institute
Expert-curated CS & AI curriculum aligned to CBSE standards. A bharath.ai initiative. About Us

Competitive Programming: Think Fast, Code Faster

📚 Graph Algorithms & Advanced DS⏱️ 22 min read🎓 Grade 9
✍️ AI Computer Institute Editorial Team Published: March 2026 CBSE-aligned · Peer-reviewed · 22 min read
Content curated by subject matter experts with IIT/NIT backgrounds. All chapters are fact-checked against official CBSE/NCERT syllabi.

Competitive Programming: Think Fast, Code Faster

What is Competitive Programming?

Competitive programming is solving algorithmic problems under time and memory constraints. It develops problem-solving skills, teaches data structures and algorithms, and is a global competition platform.

Popular Indian Platforms

  • CodeChef: Indian platform, problems in multiple languages, contests monthly
  • Codeforces: Russian platform, very popular among Indian programmers
  • HackerRank: Interview prep and contests
  • HackerEarth: Contests with college hackathons
  • ZCO/INOI: Indian National Olympiad in Informatics - school-level competitions
  • ICPC: International Collegiate Programming Contest

Time Complexity Analysis

Big O Notation


# Rule of thumb: 10^8 operations per second
# n = 10^6: need O(n log n) or better
# n = 10^4: can afford O(n^2)
# n = 100: can afford O(n^3) or even O(n^4)

# Common complexities
# O(1) - constant
def access_array(arr, index):
    return arr[index]

# O(log n) - logarithmic
def binary_search(arr, target):
    left, right = 0, len(arr) - 1
    while left <= right:
        mid = (left + right) // 2
        if arr[mid] == target:
            return mid
        elif arr[mid] < target:
            left = mid + 1
        else:
            right = mid - 1
    return -1

# O(n) - linear
def linear_search(arr, target):
    for num in arr:
        if num == target:
            return True
    return False

# O(n log n) - linearithmic
def merge_sort(arr):
    if len(arr) <= 1:
        return arr
    mid = len(arr) // 2
    left = merge_sort(arr[:mid])
    right = merge_sort(arr[mid:])
    return merge(left, right)

# O(n^2) - quadratic
def bubble_sort(arr):
    n = len(arr)
    for i in range(n):
        for j in range(n - 1 - i):
            if arr[j] > arr[j + 1]:
                arr[j], arr[j + 1] = arr[j + 1], arr[j]
    return arr

# O(2^n) - exponential (avoid!)
def fibonacci_naive(n):
    if n <= 1:
        return n
    return fibonacci_naive(n-1) + fibonacci_naive(n-2)

# Complexity table for different n
import time
print("Time Limit Exceeded (TLE) if time > 1-2 seconds")
print("n=10: O(n^5) = 100,000 ops ✓")
print("n=100: O(n^3) = 1,000,000 ops ✓")
print("n=1,000: O(n^2) = 1,000,000 ops ✓")
print("n=10,000: O(n log n) ≈ 130,000 ops ✓")
print("n=100,000: O(n) = 100,000 ops ✓")
print("n=1,000,000: O(log n) ≈ 20 ops ✓")

Two Pointers Technique

Use two pointers moving towards each other or same direction to solve array problems in O(n).

Example: Two Sum II (Sorted Array)


def two_sum_sorted(arr, target):
    """Find two numbers that sum to target in sorted array"""
    left = 0
    right = len(arr) - 1
    
    while left < right:
        current_sum = arr[left] + arr[right]
        if current_sum == target:
            return [left + 1, right + 1]  # 1-indexed
        elif current_sum < target:
            left += 1
        else:
            right -= 1
    
    return []

# Test
arr = [2, 7, 11, 15]
print(two_sum_sorted(arr, 9))  # [1, 2]

Example: Container With Most Water


def max_area(heights):
    """Find max water area between two bars - O(n)"""
    left = 0
    right = len(heights) - 1
    max_area_val = 0
    
    while left < right:
        width = right - left
        area = width * min(heights[left], heights[right])
        max_area_val = max(max_area_val, area)
        
        if heights[left] < heights[right]:
            left += 1
        else:
            right -= 1
    
    return max_area_val

# Test: bars at heights [1,8,6,2,5,4,8,3,7]
print(max_area([1, 8, 6, 2, 5, 4, 8, 3, 7]))  # 49

Sliding Window Technique

Maintain a window of fixed or variable size, slide it across array/string.

Maximum Sum of Subarray (Fixed Window)


def max_sum_k_subarray(arr, k):
    """Max sum of k consecutive elements - O(n)"""
    if k > len(arr):
        return 0
    
    # Calculate first window
    window_sum = sum(arr[:k])
    max_sum = window_sum
    
    # Slide the window
    for i in range(k, len(arr)):
        window_sum = window_sum - arr[i - k] + arr[i]
        max_sum = max(max_sum, window_sum)
    
    return max_sum

# Test
arr = [1, 4, 2, 10, 2, 3, 1, 0, 20]
print(max_sum_k_subarray(arr, 4))  # 24 (10+2+3+1+8 nope... 4+2+10+2=18? no)
# Actually: 2+3+1+0+20=26? No. 4+2+10+2=18, 2+10+2+3=17, 10+2+3+1=16, 2+3+1+0=6, 3+1+0+20=24 ✓

Longest Substring Without Repeating Characters (Variable Window)


def longest_substring_no_repeat(s):
    """Find longest substring with unique characters - O(n)"""
    char_index = {}
    max_length = 0
    left = 0
    
    for right in range(len(s)):
        if s[right] in char_index and char_index[s[right]] >= left:
            left = char_index[s[right]] + 1
        
        char_index[s[right]] = right
        max_length = max(max_length, right - left + 1)
    
    return max_length

# Test
print(longest_substring_no_repeat("abcabcbb"))  # 3 (abc)
print(longest_substring_no_repeat("bbbbb"))     # 1 (b)
print(longest_substring_no_repeat("pwwkew"))    # 3 (wke)

Greedy Algorithm

Make locally optimal choices hoping to find global optimum.

Activity Selection Problem


def activity_selection(activities):
    """Select max non-overlapping activities - O(n log n)"""
    # activities = [(start, end), ...]
    # Sort by end time
    activities.sort(key=lambda x: x[1])
    
    selected = [activities[0]]
    
    for i in range(1, len(activities)):
        # If start time >= last selected end time, no overlap
        if activities[i][0] >= selected[-1][1]:
            selected.append(activities[i])
    
    return selected

# Example: school class schedule
activities = [(9, 10), (9, 11), (10, 11), (11, 12), (10, 13)]
print(activity_selection(activities))  # [(9, 10), (10, 11), (11, 12)]

Fractional Knapsack Problem


def fractional_knapsack(items, capacity):
    """Take items with best value/weight ratio - O(n log n)"""
    # items = [(weight, value), ...]
    # Sort by value/weight ratio (descending)
    items.sort(key=lambda x: x[1] / x[0], reverse=True)
    
    total_value = 0
    remaining_capacity = capacity
    
    for weight, value in items:
        if weight <= remaining_capacity:
            remaining_capacity -= weight
            total_value += value
        else:
            total_value += (remaining_capacity / weight) * value
            break
    
    return total_value

# Example: jewelry heist
items = [(10, 100), (20, 200), (30, 150)]  # (weight, value)
capacity = 30
print(fractional_knapsack(items, capacity))  # 400

Problem-Solving Strategies

  1. Understand the problem: Read carefully, identify input/output, constraints
  2. Think of examples: Work through small examples by hand
  3. Identify pattern: Look for repeating structure, known algorithms
  4. Code and test: Implement, test with edge cases
  5. Optimize: Improve time/space complexity if needed

Example Problem Analysis


# Problem: Given array, find element that appears > n/3 times
# Constraints: n <= 10^5, time limit: 1 second

# Approach 1: Brute force - O(n^2) ✗ Too slow
def find_majority_slow(arr):
    for num in arr:
        count = arr.count(num)
        if count > len(arr) // 3:
            return num

# Approach 2: Hash map - O(n) space, O(n) time ✓ Good
def find_majority_hash(arr):
    count = {}
    for num in arr:
        count[num] = count.get(num, 0) + 1
    
    for num, cnt in count.items():
        if cnt > len(arr) // 3:
            return num

# Approach 3: Boyer-Moore voting - O(n) time, O(1) space ✓ Optimal
def find_majority_voting(arr):
    candidate1, candidate2 = None, None
    count1, count2 = 0, 0
    
    for num in arr:
        if num == candidate1:
            count1 += 1
        elif num == candidate2:
            count2 += 1
        elif count1 == 0:
            candidate1, count1 = num, 1
        elif count2 == 0:
            candidate2, count2 = num, 1
        else:
            count1 -= 1
            count2 -= 1
    
    return candidate1 if arr.count(candidate1) > len(arr) // 3 else candidate2

Common Patterns in Competitive Programming

PatternUse CaseComplexityExamples
Two PointersSorted arrays, palindromesO(n)Two sum, merge sorted arrays
Sliding WindowSubarray/substring problemsO(n)Max sum, longest substring
BFS/DFSGraphs, treesO(V+E)Shortest path, connected components
Binary SearchSorted data, monotonicO(log n)Find element, rotated array
GreedyOptimization problemsVariesActivity selection, Huffman coding
DPOptimization with subproblemsVariesFibonacci, coin change, knapsack

India Context: Competitive Programming Scene

CodeChef

Indian platform founded in 2009. Hosts monthly contests with problems for all skill levels. Large Indian community, prizes for top performers.

ZCO/INOI (Zonal Computing Olympiad / Indian National Olympiad in Informatics)

School-level competition in India. Gateway to IOI (International Olympiad in Informatics). Three stages: ZCO → INOI → IOI.

ICPC in India

Asia-Bangalore, Asia-Kolkata, Asia-Chennai regions host ICPC. Indian teams regularly qualify for World Finals.

Practice Problems (CodeChef Style)

  1. FLOW008: Find average of n numbers (warm-up)
  2. CHFBARN: Cow barn painting (greedy + simulation)
  3. STICKS: Minimize total cutting (greedy algorithm)
  4. MAXFUN: Maximize function value (observation + formula)
  5. LUNCHTIME: Find minimum and second minimum

Key Takeaways

  • Time complexity is crucial - 10^8 operations per second is typical
  • Two pointers and sliding window solve many array/string problems in O(n)
  • Greedy works when locally optimal choice leads to global optimum
  • Always code with edge cases and constraints in mind
  • Practice on CodeChef, Codeforces, HackerEarth regularly
  • Learn standard algorithms: BFS, DFS, binary search, DP, greedy
  • Read problem carefully - many WA (wrong answers) from misunderstanding
  • Contest tips: Code fast, test thoroughly, optimize if needed, then submit

From Concept to Reality: Competitive Programming: Think Fast, Code Faster

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.

Competitive Programming: Think Fast, Code Faster 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).

Did You Know?

🚀 ISRO is the world's 4th largest space agency, powered by Indian engineers. With a budget smaller than some Hollywood blockbusters, ISRO does things that cost 10x more for other countries. The Mangalyaan (Mars Orbiter Mission) proved India could reach Mars for the cost of a film. Chandrayaan-3 succeeded where others failed. This is efficiency and engineering brilliance that the world studies.

🏥 AI-powered healthcare diagnosis is being developed in India. Indian startups and research labs are building AI systems being tested for detecting conditions like cancer and retinopathy from medical images, with some studies showing promising early results (e.g., Google Health's 2020 Nature study on mammography screening). These systems are being deployed in rural clinics across India, bringing world-class healthcare to millions who otherwise could not afford it.

🌾 Agriculture technology is transforming Indian farming. Drones with computer vision scan crop health. IoT sensors in soil measure moisture and nutrients. AI models predict yields and optimal planting times. Companies like Ninjacart and SoilCompanion are using these technologies to help farmers access better market pricing through AI-driven platforms. This is computer science changing millions of lives in real-time.

💰 India has more coding experts per capita than most Western countries. India hosts platforms like CodeChef, which has over 15 million users worldwide. Indians dominate competitive programming rankings. Companies like Flipkart and Razorpay are building world-class engineering cultures. The talent is real, and if you stick with computer science, you will be part of this story.

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.

The Process: How Competitive Programming: Think Fast, Code Faster Works in Production

In professional engineering, implementing competitive programming: think fast, code faster requires a systematic approach that balances correctness, performance, and maintainability:

Step 1: Requirements Analysis and Design Trade-offs
Start with a clear specification: what does this system need to do? What are the performance requirements (latency, throughput)? What about reliability (how often can it fail)? What constraints exist (memory, disk, network)? Engineers create detailed design documents, often including complexity analysis (how does the system scale as data grows?).

Step 2: Architecture and System Design
Design the system architecture: what components exist? How do they communicate? Where are the critical paths? Use design patterns (proven solutions to common problems) to avoid reinventing the wheel. For distributed systems, consider: how do we handle failures? How do we ensure consistency across multiple servers? These questions determine the entire architecture.

Step 3: Implementation with Code Review and Testing
Write the code following the architecture. But here is the thing — it is not a solo activity. Other engineers read and critique the code (code review). They ask: is this maintainable? Are there subtle bugs? Can we optimize this? Meanwhile, automated tests verify every piece of functionality, from unit tests (testing individual functions) to integration tests (testing how components work together).

Step 4: Performance Optimization and Profiling
Measure where the system is slow. Use profilers (tools that measure where time is spent). Optimize the bottlenecks. Sometimes this means algorithmic improvements (choosing a smarter algorithm). Sometimes it means system-level improvements (using caching, adding more servers, optimizing database queries). Always profile before and after to prove the optimization worked.

Step 5: Deployment, Monitoring, and Iteration
Deploy gradually, not all at once. Run A/B tests (comparing two versions) to ensure the new system is better. Once live, monitor relentlessly: metrics dashboards, logs, traces. If issues arise, implement circuit breakers and graceful degradation (keeping the system partially functional rather than crashing completely). Then iterate — version 2.0 will be better than 1.0 based on lessons learned.


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.

Real Story from India

The India Stack Revolution

In the early 1990s, India's economy was closed. Indians could not easily send money abroad or access international services. But starting in 1991, India opened its economy. Young engineers in Bangalore, Hyderabad, and Chennai saw this as an opportunity. They built software companies (Infosys, TCS, Wipro) that served the world.

Fast forward to 2008. India had a problem: 500 million Indians had no formal identity. No bank account, no passport, no way to access government services. The government decided: let us use technology to solve this. UIDAI (Unique Identification Authority of India) was created, and engineers designed Aadhaar.

Aadhaar collects fingerprints and iris scans from every Indian, stores them in massive databases using sophisticated encryption, and allows anyone (even a street vendor) to verify identity instantly. Today, 1.4 billion Indians have Aadhaar. On top of Aadhaar, engineers built UPI (digital payments), Jan Dhan (bank accounts), and ONDC (open e-commerce network).

This entire stack — Aadhaar, UPI, Jan Dhan, ONDC — is called the India Stack. It is considered the most advanced digital infrastructure in the world. Governments and companies everywhere are trying to copy it. And it was built by Indian engineers using computer science concepts that you are learning right now.

Production Engineering: Competitive Programming: Think Fast, Code Faster at Scale

Understanding competitive programming: think fast, code faster 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.

Checkpoint: Test Your Understanding 🎯

Before moving forward, ensure you can answer these:

Question 1: Summarize competitive programming: think fast, code faster in 3-4 sentences. Include: what problem it solves, how it works at a high level, and one real-world application.

Answer: A strong summary should mention the core mechanism, not just the name. If you can explain it to someone who has never heard of it, you understand it.

Question 2: Walk through a concrete example of competitive programming: think fast, code faster with actual data or numbers. Show each step of the process.

Answer: Use a small example (3-5 data points or a simple scenario) and trace through every step. This is how competitive exams test understanding.

Question 3: What are 2-3 limitations of competitive programming: think fast, code faster? In what situations would you choose a different approach instead?

Answer: Every technique has weaknesses. Knowing when NOT to use something is as important as knowing how it works.

Key Vocabulary

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

Class: A blueprint for creating objects with shared properties and methods
Object: An instance of a class with its own data and behaviour
Inheritance: When a new class inherits properties and methods from an existing class
Recursion: A function that calls itself to solve smaller sub-problems
Stack: A data structure where the last item added is the first removed (LIFO)

💡 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 competitive programming: think fast, code faster 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 8–9 • Graph Algorithms & Advanced DS • Aligned with NEP 2020 & CBSE Curriculum

← Dynamic Programming: Solving Problems by RememberingWhat is Machine Learning? Teaching Computers to Learn →
🔥 4× Challenge

Found this useful? Share it!

📱 WhatsApp 🐦 Twitter 💼 LinkedIn