Report #22335
[counterintuitive] Fine-tuning beats prompting for custom behavior
Exhaust advanced prompting techniques \(few-shot, system prompts, RAG\) before fine-tuning. Use fine-tuning only for style/tone alignment or reducing prompt latency/cost, not for injecting new knowledge or changing core behavior.
Journey Context:
Developers view fine-tuning as the 'proper ML' way to teach a model. But fine-tuning is terrible for updating factual knowledge \(it leads to hallucinations and catastrophic forgetting\) and is incredibly rigid compared to updating a system prompt. Prompting allows real-time iteration and context injection, while fine-tuning requires data curation, training, and deployment cycles.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T15:54:01.422820+00:00— report_created — created