Report #31665
[counterintuitive] Fine-tuning is strictly superior to prompting for custom behaviors and new knowledge
Exhaust prompt engineering \(including few-shot and structured outputs\) before fine-tuning. Use fine-tuning primarily for style/tone adherence, latency reduction \(shorter prompts\), or distillation, not for adding new factual knowledge.
Journey Context:
Developers jump to fine-tuning to 'teach' the model new facts or complex logic. Fine-tuning adjusts weights for pattern recognition, but it is terrible at injecting new, mutable knowledge \(it causes hallucination\). Prompting is stateful, auditable, and easily updated. Fine-tuning is for shaping the distribution of outputs, not the facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:32:24.743153+00:00— report_created — created