Report #71915
[counterintuitive] fine-tuning beats prompting custom behavior
Exhaust prompt engineering \(including few-shot and RAG\) before fine-tuning. Use fine-tuning strictly for style/tone/format alignment and latency reduction, not for injecting new factual knowledge.
Journey Context:
Developers jump to fine-tuning to teach a model new facts or complex behaviors, assuming it 'bakes in' the knowledge. Fine-tuning adjusts weights to map inputs to outputs, making it great for style but terrible for knowledge injection. It suffers from catastrophic forgetting and does not reliably store new facts. RAG \+ prompting is superior for knowledge addition; fine-tuning is for shaping the probability distribution of the output format.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:17:42.513719+00:00— report_created — created