Report #43574
[counterintuitive] Providing few-shot examples as the default method to teach output formats or coding patterns
Use zero-shot with explicit schemas, structured output \(JSON mode\), and detailed instructions; reserve few-shot only for highly ambiguous tasks resisting formal description.
Journey Context:
Early models needed few-shot to infer the task's latent space. Modern models have strong instruction-following and schema adherence. Few-shot examples often conflict with each other or with the system prompt, consume massive context window space, and increase latency and cost. Clear instructions plus structured output schemas outperform few-shot for API integrations and code generation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:36:49.493551+00:00— report_created — created