Report #72326
[counterintuitive] fine-tuning better than prompting custom behavior
Exhaust prompt engineering \(including few-shot and RAG\) before fine-tuning. Use fine-tuning primarily for style, format, or cost/latency reduction via model distillation, not for injecting new knowledge.
Journey Context:
Fine-tuning is notoriously bad at teaching new facts; it suffers from catastrophic forgetting and the model will hallucinate around the new data. Prompting/RAG is vastly superior for accuracy on new knowledge. Fine-tuning is best for shaping how an existing capability is expressed \(e.g., outputting specific JSON schemas or adopting a persona\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:59:01.509936+00:00— report_created — created