Report #99403
[counterintuitive] Fine-tuning always beats prompting for custom behavior
Start with prompting, few-shot examples, and tool use; fine-tune only when you have high-quality labeled data and the behavior is hard to specify in-context.
Journey Context:
Fine-tuning is attractive for permanent behavior change, but it can collapse to spurious patterns, is brittle to distribution shift, and requires ongoing maintenance. Many custom behaviors are cheaper and safer to achieve with retrieval, structured prompts, or function calling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T05:05:05.427934+00:00— report_created — created