Overlapping Subproblems and Optimal Substructure in DSA Go - Build from Scratch

Understanding Overlapping Subproblems and Optimal Substructure with Fibonacci

📖 Scenario: Imagine you want to find the number of ways to climb stairs where you can take 1 or 2 steps at a time. This is like the Fibonacci sequence. Calculating it directly repeats many calculations. We will learn how to store results to avoid repeating work, showing overlapping subproblems and optimal substructure.

🎯 Goal: Build a Go program that calculates Fibonacci numbers using memoization to demonstrate overlapping subproblems and optimal substructure.

📋 What You'll Learn

Create a map to store Fibonacci results

Create a variable for the target Fibonacci number

Write a recursive function with memoization to calculate Fibonacci

Print the Fibonacci number for the target

💡 Why This Matters

🌍 Real World

Memoization is used in many algorithms to optimize repeated calculations, such as in dynamic programming problems, route planning, and resource allocation.

💼 Career

Understanding overlapping subproblems and optimal substructure helps in writing efficient algorithms, a key skill for software engineers and data scientists.

1

Create a map to store Fibonacci results

Create a map called memo of type map[int]int to store Fibonacci numbers already calculated.

DSA Go

var memo map[int]int
// Your code here

Hint

Use make(map[int]int) to create the map.

2

Create a variable for the target Fibonacci number

Create an integer variable called n and set it to 10 to represent the Fibonacci number to calculate.

DSA Go

var memo = make(map[int]int)
var n int
// Your code here

Hint

Set n to 10 to find the 10th Fibonacci number.

3

Write a recursive function with memoization to calculate Fibonacci

Write a function called fib that takes an integer num and returns an integer. Use memo to store and reuse results. If num is 0 or 1, return num. Otherwise, check if num is in memo. If yes, return the stored value. If not, calculate fib(num-1) + fib(num-2), store it in memo[num], and return it.

DSA Go

var memo = make(map[int]int)
var n int = 10

func fib(num int) int {
    // Your code here
}

Hint

Use recursion and check memo before calculating.

4

Print the Fibonacci number for the target

Write a main function that prints the result of fib(n).

DSA Go

var memo = make(map[int]int)
var n int = 10

func fib(num int) int {
    if num == 0 || num == 1 {
        return num
    }
    if val, ok := memo[num]; ok {
        return val
    }
    memo[num] = fib(num-1) + fib(num-2)
    return memo[num]
}

func main() {
    // Your code here
}

Hint

Use fmt.Println(fib(n)) inside main.

Practice

1. Which of the following best describes the Overlapping Subproblems property in dynamic programming?

easy

A. The problem requires sorting before solving.

B. The problem has a unique solution without repeating any subproblems.

C. The problem can be broken down into smaller subproblems which are solved multiple times.

D. The problem can only be solved using recursion without memoization.

Solution

1. Step 1: Understand Overlapping Subproblems

   Overlapping subproblems means the same smaller problems appear multiple times during the solution process.

2. Step 2: Match the definition with options

   The problem can be broken down into smaller subproblems which are solved multiple times. correctly states that subproblems are solved multiple times, which is the key idea behind overlapping subproblems.

3. Final Answer:

   The problem can be broken down into smaller subproblems which are solved multiple times. -> Option C

4. Quick Check:

   Overlapping Subproblems = repeated smaller problems [OK]

Hint: Look for repeated smaller problems solved multiple times [OK]

Common Mistakes:

• Confusing overlapping subproblems with unique subproblems
• Thinking sorting is required for overlapping subproblems
• Assuming recursion alone solves overlapping subproblems

2. Which Go code snippet correctly declares a memoization map for storing integer results keyed by integer inputs?

easy

A. memo := make([]int, 10)

B. memo := map[string]int{}

C. memo := []int{}

D. memo := make(map[int]int)

Solution

1. Step 1: Identify correct map declaration for memoization

   Memoization requires a map with keys and values. Here keys and values are integers.

2. Step 2: Check each option

   memo := make(map[int]int) uses make(map[int]int) which creates a map with int keys and int values, perfect for memoization.

3. Final Answer:

   memo := make(map[int]int) -> Option D

4. Quick Check:

   Map[int]int for memoization = memo := make(map[int]int) [OK]

Hint: Use make(map[int]int) for int-to-int memo maps [OK]

Common Mistakes:

• Using slices instead of maps for memoization
• Using wrong key types like string when int is needed
• Confusing slice initialization with map initialization

3. What is the output of the following Go code implementing Fibonacci with memoization?

package main
import "fmt"

func fib(n int, memo map[int]int) int {
    if n <= 1 {
        return n
    }
    if val, ok := memo[n]; ok {
        return val
    }
    memo[n] = fib(n-1, memo) + fib(n-2, memo)
    return memo[n]
}

func main() {
    memo := make(map[int]int)
    fmt.Println(fib(5, memo))
}

medium

A. 5

B. 8

C. 3

D. 13

Solution

1. Step 1: Understand Fibonacci calculation with memo

   fib(5) = fib(4) + fib(3), and so on, with memo storing results to avoid repeats.

2. Step 2: Calculate fib(5)

   fib(0)=0, fib(1)=1, fib(2)=1, fib(3)=2, fib(4)=3, fib(5)=5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   fib(5) = 5 [OK]

Hint: Recall Fibonacci sequence: 0,1,1,2,3,5,8... [OK]

Common Mistakes:

• Confusing fib(5) with fib(6)
• Ignoring memoization effect and recalculating
• Mixing up base cases n<=1

4. Identify the bug in this Go code snippet for memoized Fibonacci:

func fib(n int, memo map[int]int) int {
    if n == 0 {
        return 0
    }
    if n == 1 {
        return 1
    }
    if val, ok := memo[n]; ok {
        return val
    }
    memo[n] = fib(n-1, memo) + fib(n-2, memo)
    return memo[n]
}

medium

A. Memo map is not initialized before use

B. Base case should be n <= 1 instead of separate checks

C. Base case for n == 0 is missing

D. Function does not return memo[n] after calculation

Solution

1. Step 1: Check base cases and memo usage

   Base cases for n==0 and n==1 are correctly handled. Memo is used properly inside function.

2. Step 2: Identify initialization issue

   The function expects memo map passed in, but if not initialized before calling, it causes runtime error.

3. Final Answer:

   Memo map is not initialized before use -> Option A

4. Quick Check:

   Uninitialized map causes runtime panic [OK]

Hint: Always initialize maps before passing to functions [OK]

Common Mistakes:

• Assuming base cases are wrong when they are correct
• Forgetting to initialize memo map before first call
• Missing return statement after memo assignment

5. You want to find the minimum cost path in a grid from top-left to bottom-right, moving only right or down. The cost grid is:

cost := [][]int{
  {1, 3, 5},
  {2, 1, 2},
  {4, 3, 1},
}

Which approach best uses Overlapping Subproblems and Optimal Substructure to solve this efficiently?

hard

A. Use recursion without memoization to explore all paths

B. Use dynamic programming with a 2D memo table storing minimum cost to each cell

C. Sort the grid and pick the smallest costs in order

D. Use a greedy approach picking the smallest cost neighbor at each step

Solution

1. Step 1: Understand problem properties

   Minimum cost path has optimal substructure: minimum cost to a cell depends on minimum cost to neighbors.

2. Step 2: Choose approach using overlapping subproblems

   Dynamic programming with a 2D memo table stores results of subproblems (cells), avoiding repeated calculations.

3. Final Answer:

   Use dynamic programming with a 2D memo table storing minimum cost to each cell -> Option B

4. Quick Check:

   DP with memo table = efficient solution [OK]

Hint: Use DP table to store subproblem results for grid paths [OK]

Common Mistakes:

• Trying recursion without memo causes exponential time
• Sorting grid ignores path constraints
• Greedy approach may miss global minimum path