Week 8 · 1-D Dynamic Programming

Word Break

Solve Word Break by recognizing the 1-D Dynamic Programming pattern and turning the prompt into a small invariant before coding.

Medium 1-D Dynamic Programming Week 8 Practice runner

Frame the problem

Implement word_break with the exact signature used by the interactive runner.
Use the visible tests to confirm the input and output shape before reading the final solution.
Treat challenge tests as edge-case pressure: empty inputs, repeated values, boundary shapes, or impossible states.
State the invariant before code, then dry-run one passing case and one failing-looking case.

1. Reveal example inputs and outputs

Example 1

Input:

word_break("leetcode", [
  "leet",
  "code"
])

Output:

true

2. Brute force first

What direct brute force would be correct for a tiny input? Name the exact repeated work that the target pattern removes.

3. Reveal the insight ladder

Map the prompt to the 1-D Dynamic Programming pattern instead of starting from syntax.
dp[i] means the prefix ending at i can be segmented.
Every final split must leave a valid prefix behind it.
Only reveal the final code after you can explain why each state update is safe.

4. Dry run before code

word-break-true: input ["leetcode",["leet","code"]] should produce true. Hint to check your state: dp[i] means the prefix ending at i can be segmented.
word-break-false: input ["catsandog",["cats","dog","sand","and","cat"]] should produce false. Hint to check your state: Every final split must leave a valid prefix behind it.

5. Reveal final Python solution

def word_break(s: str, word_dict: list[str]) -> bool:
    words = set(word_dict)
    dp = [False] * (len(s) + 1)
    dp[0] = True
    for end in range(1, len(s) + 1):
        for start in range(end):
            if dp[start] and s[start:end] in words:
                dp[end] = True
                break
    return dp[-1]

Complexity: Derive the exact bounds from word_break: count how often each input item is visited and the maximum size of the main state structure.

Interview narration

I will first describe the invariant in plain language.
Then I will explain what data structure carries that invariant across the traversal, loop, recursion, or DP transition.
Finally I will walk one edge case before writing the optimized version.

Common traps

Solving only the visible example instead of the invariant.
Forgetting empty input, singleton input, duplicate values, or impossible-state cases.
Revealing the solution before doing a dry run from the starter signature.

Follow-up drills

1. How do you turn this into a timed interview answer?

Start with the invariant, give the brute force in one sentence, name the optimized state, code the core loop or recursion, and run one visible test aloud before mentioning complexity.

2. How do you scale the same pattern to a larger input?

Track which state grows with the input: hash maps and sets grow with distinct values, queues grow with frontier width, recursion grows with depth, heaps grow with active candidates, and DP tables grow with state count.

3. What should you practice from blank tomorrow?

Rewrite word_break without looking at the solution, then compare only the invariant and state updates before checking syntax.

Interactive runner

Write the required Python function. Your code runs locally in this browser. Hints reveal one failing case at a time.