Report #43232
[counterintuitive] fine-tuning better than prompting custom behavior
Exhaust prompt engineering and dynamic few-shot examples before fine-tuning. Use fine-tuning primarily for style, format adherence, or latency/cost reduction \(distillation\), not for injecting new factual knowledge.
Journey Context:
Developers jump to fine-tuning to teach a model new behaviors or facts, viewing prompting as a limited workaround. Fine-tuning is notoriously bad at injecting new factual knowledge \(often causing new hallucinations\) and is brittle if task requirements change. Prompting and few-shot examples are vastly more flexible, debuggable, and often achieve equivalent or better task adherence for custom behaviors without the overhead of training data curation and model management.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T03:02:17.565082+00:00— report_created — created