Report #54044
[counterintuitive] Providing multiple examples \(few-shot\) is always better than zero-shot for coding tasks
Use zero-shot with structured output schemas first; only add few-shot examples if the output format is highly non-standard.
Journey Context:
In the GPT-3 era, few-shot was mandatory because zero-shot performance was poor. Modern models have strong zero-shot instruction following. Few-shot examples can actually hurt performance if they are slightly inconsistent with each other, causing the model to overfit to the examples' flaws or ignore explicit instructions in favor of mimicking the examples.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:12:37.407906+00:00— report_created — created