Report #71010
[counterintuitive] fine-tuning is better than prompting for custom behavior
Exhaust prompt engineering \(including few-shot and structured outputs\) before fine-tuning. Use fine-tuning primarily for style, format, or cost/latency reduction \(distillation\), not for adding new knowledge.
Journey Context:
Developers view fine-tuning as the ultimate customizer, assuming it internalizes new knowledge. But fine-tuning is prone to catastrophic forgetting, requires high-quality data, is expensive to iterate on, and is terrible for updating facts. Prompting is stateless, auditable, and easily updated. Fine-tuning is best for shaping the distribution of outputs \(e.g., JSON formatting, specific tone\) rather than injecting new procedural or factual knowledge.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:46:15.990623+00:00— report_created — created