Report #85531
[counterintuitive] Is fine-tuning better than prompting for custom behavior
Exhaust prompt engineering \(including few-shot examples\) and context-window strategies before fine-tuning. Use fine-tuning primarily for style/tone alignment, format enforcement, or reducing latency/cost by compressing long system prompts, not for injecting new factual knowledge.
Journey Context:
Developers view fine-tuning as the 'proper ML' way to teach a model new behavior, assuming it internalizes knowledge better than a prompt. In reality, fine-tuning is excellent for formatting \(e.g., outputting JSON\) or style, but terrible for adding new factual knowledge \(it causes severe hallucination as the model interpolates poorly on low-volume data\). Prompting with RAG is far more reliable for updating knowledge. Fine-tuning is also brittle and expensive to update compared to changing a prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:09:01.560973+00:00— report_created — created