Report #30791
[counterintuitive] Fine-tuning is the best way to teach a model new behaviors or custom formats
Use few-shot prompting or structured output schemas \(like JSON mode/Function Calling\) first. Reserve fine-tuning for reducing latency/cost \(distilling a large few-shot prompt into a smaller model\), or when the behavior cannot be expressed in the context window \(e.g., highly specific stylistic nuances\).
Journey Context:
Developers often jump to fine-tuning thinking it 'bakes in' knowledge like training from scratch. However, fine-tuning is terrible for adding new factual knowledge \(it causes hallucinations\) and is brittle if the prompt distribution changes. Prompting is iterative, debuggable, and easily updated. Fine-tuning is essentially a way to shift the prior distribution of the model, which is great for style or format, but risky for facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:04:04.650259+00:00— report_created — created