Graph Traversal: A Practical Guide to DFS and BFS

Graph traversal is fundamental to solving many algorithmic problems. Understanding DFS and BFS is key.

Depth-First Search (DFS)

DFS explores as far as possible along each branch before backtracking.

Recursive Implementation

def dfs_recursive(graph, node, visited):
    visited.add(node)
    print(node)
    
    for neighbor in graph[node]:
        if neighbor not in visited:
            dfs_recursive(graph, neighbor, visited)

Iterative Implementation

def dfs_iterative(graph, start):
    visited = set()
    stack = [start]
    
    while stack:
        node = stack.pop()
        if node not in visited:
            visited.add(node)
            print(node)
            stack.extend(reversed(graph[node]))

Breadth-First Search (BFS)

BFS explores all neighbors before moving to the next level.

from collections import deque

def bfs(graph, start):
    visited = set()
    queue = deque([start])
    visited.add(start)
    
    while queue:
        node = queue.popleft()
        print(node)
        
        for neighbor in graph[node]:
            if neighbor not in visited:
                visited.add(neighbor)
                queue.append(neighbor)

When to reach for each style

DFS is a strong default when

• you care about paths or backtracking structure
• you need cycle detection or topological ordering
• recursion depth is safe for your graph size

BFS shines when

• you need shortest paths on an unweighted graph
• you want a clean level-by-level traversal
• you are counting minimum steps in a small state space

Common applications

1. DFS shows up in maze solving, cycle detection, and topological sort.
2. BFS shows up in shortest paths, level-order traversal, and many social-graph questions.

Both stay essential tools in your algorithmic toolkit.

How to practice this skill

Treat this topic as a loop rather than a fact to memorize. First, name the pattern in plain English. Then write the smallest version that proves you understand the invariant. Only after that should you chase speed. That order matters because most interview mistakes are not typing mistakes; they are recognition mistakes. You reach for the right data structure too late, or you optimize before you have named what must stay true.

For graphs practice, the useful repetition is spaced. Solve one problem slowly, rewrite the solution from memory the next day, then do a timed variant after the idea feels boring. The second pass is where the pattern moves from recognition to recall. The timed pass is where it becomes usable under pressure.

Implementation checklist

• Restate the input and output before coding.
• Write down the invariant or decision rule in one sentence.
• Test the smallest case, the largest obvious case, and the case that breaks the naive approach.
• Compare the final complexity to the constraint that actually matters.

The checklist is intentionally short. A long checklist becomes another thing to memorize. A short one becomes a rhythm you can run in a blank editor, in a live interview, or in an AlgoArena battle.

Edge cases worth drilling

Most missed solutions come from one of three places: empty input, duplicated values, or a boundary that looks harmless until the loop reaches it. When you review a solution, do not only ask whether it passed. Ask which boundary made the implementation honest.

If a solution uses indexes, trace the first and last iteration. If it uses a map or set, trace the duplicate case. If it uses recursion, name the base case and the state that gets smaller. These small reviews are faster than solving a new problem and often teach more.

How it transfers to real work

The interview version is compact, but the habit transfers. Production bugs often come from the same failure mode: unclear invariants under changing data. A developer who can name the invariant, test the boundary, and explain the tradeoff is easier to trust than someone who only remembers a trick.

That is why AlgoArena treats practice as observable work. The point is not to collect solved badges. The point is to build a repeatable way of thinking that survives a clock, an unfamiliar prompt, and another person reading over your shoulder.

Review drill

Before you move on, turn the idea into a small review drill. Pick one representative problem and write three things before you code: the pattern name, the data structure you expect to use, and the edge case that would make the naive version fail. After you solve it, rewrite the explanation in two sentences without looking at the code.

That last step is the difference between recognizing a solution and owning it. If you can explain why the approach works, you can usually rebuild it under pressure. If you only remember the final code shape, the next variant will feel like a new problem.

On AlgoArena, pair this with a timed rep only after the slow explanation is clean. Speed is useful when it compresses a skill you already understand. It is noisy when it hides the fact that the invariant was never clear.

One-session exercise

End with one mixed rep. Choose a problem where the pattern is present but not named in the title. Spend five minutes identifying the signal, ten minutes coding, and five minutes writing a post-solve note about what made the pattern recognizable. If you cannot name the signal before coding, the next best rep is not a harder problem. It is another example of the same pattern with different surface details.

That small debrief is what turns a guide into skill. You are training yourself to notice the shape before the solution is obvious.

Repeat the same exercise once with notes open and once with notes closed. The gap between those two attempts tells you whether the idea is still borrowed or has become part of your own toolkit.

If the closed-notes pass fails, keep the problem but shrink the scope: trace one loop, one recursive call, or one state transition until the reason is obvious.