Divide and Conquer — Integer Overflow at 2^30 Elements
mid = (low + high) / 2 overflows past 500M elements, causing negative indices and segfaults.
- Divide and conquer solves problems by splitting into smaller identical subproblems, solving recursively, and combining.
- Three steps: Divide (split), Conquer (solve recursively), Combine (merge).
- Complexity is driven by the combine step — O(n) combine gives O(n log n), O(1) gives O(log n).
- Master Theorem cases: compare log_b(a) to exponent c in the combine term.
- Production trap: imbalanced splits (e.g., quick sort worst-case) degrade to O(n^2).
Divide and conquer is the strategy of breaking a big problem into smaller identical subproblems, solving each independently, and combining the results. Like a general who doesn't fight every battle personally — they split the army, have each unit fight its sector, then consolidate the victory. Every recursive algorithm you know — merge sort, binary search, quick sort — is divide and conquer.
Divide and conquer is the algorithmic pattern behind merge sort, binary search, fast Fourier transform, Strassen's matrix multiplication, and closest pair of points. If you understand D&C deeply, you understand why all of these algorithms work and how to design new ones.
The pattern is deceptively simple: split the problem, solve each half, combine. The complexity depends almost entirely on the combine step — and the Master Theorem gives you an algebraic shortcut to avoid solving the recurrence from scratch each time. Learning the Master Theorem once saves you dozens of recurrence derivations throughout your career.
The Three-Step Pattern
Every divide and conquer algorithm follows the same template:
- Divide: Split the problem into subproblems (usually of equal or near-equal size)
- Conquer: Solve each subproblem recursively (base case when small enough)
- Combine: Merge subproblem solutions into the overall solution
The efficiency depends critically on the combine step. Merge sort's O(n log n) comes from an O(n) combine. Binary search has O(1) combine (no merging needed).
That's it. If you can describe your algorithm as: split, solve halves, merge results — you've got a divide and conquer. The rest is just details about how fast that merge is.
The Master Theorem
For recurrences of the form T(n) = aT(n/b) + f(n) where a ≥ 1, b > 1:
- Case 1: f(n) = O(n^(log_b(a) - ε)) → T(n) = Θ(n^log_b(a))
- Case 2: f(n) = Θ(n^log_b(a)) → T(n) = Θ(n^log_b(a) · log n)
- Case 3: f(n) = Ω(n^(log_b(a) + ε)) → T(n) = Θ(f(n))
Examples: - Merge sort: T(n) = 2T(n/2) + O(n) → Case 2 → O(n log n) - Binary search: T(n) = T(n/2) + O(1) → Case 2 → O(log n) - Strassen: T(n) = 7T(n/2) + O(n²) → Case 1 → O(n^2.807) - Simple recursion: T(n) = 2T(n/2) + O(1) → Case 1 → O(n)
Canonical Examples
These three algorithms are the classic divide and conquer triad — they show how the same pattern yields wildly different complexities depending on the combine step.
Binary Search: Divide the search space in half, conquer by checking the mid, combine is O(1) (just return mid or recurse). Result: O(log n).
Merge Sort: Divide at midpoint, conquer recursively, combine by merging two sorted halves in O(n) time. Result: O(n log n).
Fast Power: Divide exponent by 2, conquer by squaring the half-result, combine is O(1) multiplication. Result: O(log n) versus naive O(n).
The key insight: the combine step is the only thing that changes between these three. The divide and conquer skeleton stays the same.
mid = (lo + hi) // 2. In production, for arrays larger than 2^30 elements, this overflows in Java and C++. Always use mid = lo + (hi - lo) // 2.When Divide and Conquer Pays Off
D&C pays off when: 1. Subproblems are independent (no shared state to communicate) 2. Subproblems are of equal or balanced size (imbalanced splits degrade to O(n²)) 3. The combine step is efficient (O(n) or less)
- Subproblems overlap heavily (use dynamic programming instead)
- The combine step is expensive (e.g., O(n²) combine → O(n² log n) total, worse than naive)
Master Theorem Extended: When the Basic Cases Don't Apply
Not all recurrences fit the clean form T(n) = aT(n/b) + f(n). Real-world D&C algorithms often break the assumptions:
- Non-constant a or b: The number of subproblems or the split factor may vary per recursion level. Example: quick sort's pivot selection leads to varying b.
- Floating-point splits: Algorithms like Strassen's matrix multiplication split matrices into halves, but for odd dimensions you need padding — this breaks the clean n/b assumption.
- F(n) is non-polynomial: If combine is something like n log n (O(n log n)), Master Theorem's polynomial comparison fails. You need the extended case 2 with a log factor.
Akra-Bazzi Theorem handles variable subproblem sizes. For recurrences of the form T(n) = Σ a_i T(b_i n) + f(n), compute p such that Σ a_i (b_i)^p = 1. Then T(n) = Θ(n^p + n^p ∫ f(u)/u^(p+1) du).
This is rarely needed in interviews, but if you work on custom D&C algorithms (e.g., in numerical computing), it's essential.
- Works only when subproblems are equal size (b constant, a constant).
- Requires f(n) to be a polynomial or polylog.
- Case 2 has a more general form: if f(n) = Θ(n^c log^k n), then T(n) = Θ(n^c log^(k+1) n).
- When assumptions break, you must trace the recursion tree or use Akra-Bazzi.
- For interviews, 95% of questions use the basic three-case Master Theorem.
Binary Search on Rotated Array — The Overflow Bug
mid = (low + high) // 2. When low + high exceeded INT_MAX (~2^31), integer overflow produced a negative mid, causing out-of-bounds access. The array size in production hit 500 million elements.mid = low + (high - low) // 2 to avoid overflow. Also added a base case check for segment sizes < 2^20 to call a linear scan, preventing recursion deeper than log2(max array size).- Integer overflow in mid calculation is a classic bug in divide and conquer — it manifests silently at scale.
- Always use
low + (high - low) / 2to compute mid for large arrays. - Base-case termination thresholds must consider both recursion depth and input size to avoid stack overflow.
ulimit -s 65536 or set JVM -Xss4m.Key takeaways
Common mistakes to avoid
5 patternsUsing D&C when subproblems have heavy overlap
Ignoring the combine step's complexity
Using integer division for mid calculation without overflow protection
mid = low + (high - low) // 2 instead of (low + high) // 2. In languages with arbitrary precision (Python), this is safe, but in Java, C++, C# it's critical.Not handling odd-sized subproblems correctly
Creating new arrays at each recursion level
Interview Questions on This Topic
What are the three steps of divide and conquer?
Frequently Asked Questions
That's Recursion. Mark it forged?
3 min read · try the examples if you haven't