Part 0 · 2 chapters · ~12 min

Pólya's Method and Its Modern Form

George Pólya's four steps (understand, plan, carry out, look back), his heuristics, how they map to software work (requirements, design, implementation, retrospective), and why looking back is where skill compounds.

1

Four steps

Pólya wrote for mathematics students, but the steps describe every good engineering process. Requirements are understanding; design is planning; implementation is carrying out; testing and retrospectives are looking back.

PÓLYA'S FOUR STEPS
How to Solve It (1945), still the best short guide
new problem1. understandunknown, data, conditions2. planfind a connection, a related problem3. carry outcheck each step4. look backverify, generalise, reuse
swipe the figure sideways, or tap expand for full screen
1/4
understand
What is the unknown? What are the data? What is the condition? Restate the problem in your own words; draw it; name things. Most failed solutions solved a different problem.
unknown, data, conditionrestate it, draw it, name it
2

Heuristics you can use tomorrow

heuristicin software
draw a figuresketch the data flow or the state machine before coding
specialisesolve for one tenant, one currency, one record first
generalisea more general problem is sometimes easier (a rules engine instead of 30 if statements)
auxiliary problemsolve a related problem first (a prototype, a spike)
work backwardsstart from the desired output format and derive what must come before
drop a conditionsolve without the hardest constraint, then add it back