Report #46863
[counterintuitive] fine-tuning is better than prompting for custom behavior
Exhaust prompt engineering \(including few-shot and RAG\) before fine-tuning; use fine-tuning primarily for style, format, or cost/latency reduction, not for injecting new factual knowledge.
Journey Context:
Developers often jump to fine-tuning to teach a model new facts or complex behaviors, assuming it internalizes the training data. Fine-tuning is notoriously bad at injecting new knowledge—it is highly prone to hallucinating facts that loosely match the fine-tuning distribution. Prompting and RAG are vastly superior for dynamic, factual accuracy. Fine-tuning excels at shaping the distribution of outputs \(e.g., forcing JSON, adopting a specific tone, or reducing token count by distilling a long prompt\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:08:04.949104+00:00— report_created — created