Report #61656
[counterintuitive] Using few-shot examples as the default method to teach a model a new output format or task
Use zero-shot instructions combined with native structured output \(JSON schema/tool definitions\). Reserve few-shot only for stylistic imitation that defies verbal description.
Journey Context:
Few-shot was essential when models had poor instruction following. Modern models follow zero-shot instructions perfectly if structured properly. Few-shot examples often conflict with each other, constrain the model to the exact length/style of the examples \(reducing generalization\), eat up context window, and increase latency/cost. If you need a specific JSON format, defining the schema natively is 100% reliable; few-shot JSON is brittle and prone to drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:58:53.107947+00:00— report_created — created