Report #51865
[counterintuitive] Is fine-tuning always better than prompting for custom behavior
Start with prompting and RAG. Only move to fine-tuning when you need to enforce a specific output format, reduce token costs at scale, or inject a style that cannot be reliably maintained via system prompts. Fine-tuning is terrible for injecting new factual knowledge.
Journey Context:
Developers think fine-tuning is the ultimate way to teach a model new things. In reality, fine-tuning is prone to catastrophic forgetting and is surprisingly bad at learning new facts \(it adjusts weights, it doesn't add a database\). Prompting combined with RAG is far superior for knowledge addition, while fine-tuning is best for form/shape adaptation and latency/cost reduction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:33:02.769903+00:00— report_created — created