Luke a Pro

Luke Sun

Developer & Marketer

đŸ‡ș🇩
EN|缀|çč
© 2015–2026 Luke Sun.
All rights reserved.

Strategic Decision Making: Overview

| , 2 minutes reading.

Strategic Decision Making: The Master Plan

The Weight of Choice

In the previous chapters, we learned how to organize data (Trees, Hashes, Graphs). Now, we ask: “How do we solve a problem when the path is not clear?”

Life and software are full of optimization problems:

  • “What is the shortest path home?”
  • “How do I fit the most value into this limited backpack?”
  • “What is the best move in a game of chess?”

To answer these, we need a Strategy. A strategy is a high-level approach to exploring the space of possibilities without getting lost in the infinite.

The Four Pillars of Strategy

In this final section, we explore the master templates of algorithmic thought:

StrategyThe Soul / MetaphorRepresentativeBest For

MemoryThe Wise Elder
Never solves the same problem twice. Remembers the past to build the future.		Dynamic ProgrammingOptimal Solutions
Maximum profit, minimum cost.
ImpulseThe Short-Sighted Hunter
Makes the best choice right now and never looks back.		Greedy AlgorithmsEfficiency
Fast, “good enough” answers.
ExplorationThe Brave Adventurer
Tries every path, but has the courage to turn back when hitting a wall.		BacktrackingPossibilities
Puzzles, Sudoku, N-Queens.
ReductionThe Divider
Breaks a giant monster into tiny ants, then handles them one by one.		Divide & ConquerParallelism
Sorting, large-scale math.

The Three Laws of Strategy

  1. Overlapping Subproblems: If the path to the finish line involves crossing the same bridge ten times, remember the bridge! (The core of DP).
  2. Local vs. Global: Just because a choice looks good now doesn’t mean it leads to the best ending. Greedy algorithms only work when the “Local Best” is the “Global Best.”
  3. Pruning: The space of possibilities is a tree. If you know a branch leads to a cliff, cut it off early. Don’t waste time exploring the impossible.

Summary

In this section, we transition from being “Coders” to being “Architects of Logic.” We will learn that the most powerful tool in an engineer’s toolkit is not a specific language or library, but the ability to choose the right strategy for the right battle.

Let’s start with the most powerful (and feared) strategy of all: Dynamic Programming.