When to reason
Reasoning helps hard tasks but costs tokens on easy ones. Use it when:
- The task needs logic or math.
- Wrong answers are expensive.
Skip it for simple formatting or lookups.
Reason when it matters. Skip when it doesn't.
Some tasks reward the model for thinking out loud. A few well-placed nudges, step by step, then check yourself, push accuracy on anything that needs logic.
The full result is shown at the end of the exercise below.
About 1 min of reading
Reason with zero-shot or few-shot techniques
Reason zero-shot, thinking step by step.
Before you run it, say out loud what it will print. Then open the answer.
Reason few-shot from worked examples, and decide when reasoning is worth it.
Before you run it, say out loud what it will print. Then open the answer.
Reasoning helps hard tasks but costs tokens on easy ones. Use it when:
Skip it for simple formatting or lookups.
Reason when it matters. Skip when it doesn't.
You can ask a model to reason in two ways:
Zero-shot: "Think step by step."
Few-shot: give worked examples that reason.
Few-shot reasoning examples are usually stronger because the model sees the exact reasoning style you want.
"Work through this one step at a time before answering."
Telling a model to reason improves math, logic, and planning tasks.
Why it works: generating intermediate steps gives the model more to check.
answers = [prompt(input, temperature=0.8) for _ in range(5)]
winner = most_common(answers)
Running the same prompt several times and taking the majority answer reduces lucky mistakes.
Five thoughtful answers beat one quick guess.
First list what you know,
then what you need,
then solve it.
Breaking the request into reasoning stages helps the model avoid jumps.
Why it works: explicit reasoning surfaces mistakes before the final answer.
Each one is defined here on this site. Open the entry for the full definition and the other words it points at.