Report #78721
[counterintuitive] Is fine-tuning always better than prompting for custom behavior
Exhaust prompt engineering \(including few-shot and system prompts\) before fine-tuning; use fine-tuning primarily for style, format, or cost/latency reduction, not for injecting new factual knowledge.
Journey Context:
The intuition is that updating weights \(fine-tuning\) is a deeper, more robust integration than in-context learning. However, fine-tuning is notoriously bad at teaching new facts—it causes the model to hallucinate by blending new data with old weights—and is rigid compared to few-shot prompting. Fine-tuning is excellent for shaping output format or reducing token usage, but prompting remains superior for complex, multi-step behavioral instructions and dynamic updates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:43:56.561803+00:00— report_created — created