Report #86763
[counterintuitive] Is fine-tuning better than prompting for custom behaviors and styles
Exhaust prompt engineering \(including few-shot and long-context examples\) before fine-tuning; use fine-tuning primarily for latency/cost reduction or strict format adherence, not for injecting new factual knowledge.
Journey Context:
Developers jump to fine-tuning to teach the model new behaviors or knowledge. Fine-tuning is excellent for style and format, but it is surprisingly bad at injecting factual knowledge \(prone to hallucination or forgetting\). Prompting with RAG is significantly more reliable for knowledge injection. Fine-tuning also has a high maintenance cost \(retraining on updates\) and can degrade general capabilities \(catastrophic forgetting\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T04:13:21.348167+00:00— report_created — created