Report #46537
[counterintuitive] Providing few-shot examples is always superior to zero-shot instructions
Default to zero-shot with explicit instructions and structured output schemas; reserve few-shot only for highly idiosyncratic formats that resist schema definition.
Journey Context:
In the completion era, few-shot was mandatory to establish the pattern. With heavily instruction-tuned models, few-shot often introduces anchoring bias. If your examples are slightly off-distribution or contain subtle bugs, the model will faithfully replicate those errors. Few-shot also consumes massive context window, reducing the space available for the actual codebase. Modern models are highly adept at following zero-shot structural instructions \(like JSON schema\). Few-shot should be treated as a fallback for stylistic imitation, not the default for logic or formatting.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:35:01.324079+00:00— report_created — created