Report #70624
[counterintuitive] fine-tuning beats prompting for custom behavior
Exhaust prompt engineering \(including few-shot examples and structured outputs\) first. Use fine-tuning primarily for style/tone alignment, format adherence, or reducing prompt latency/cost, not for injecting new factual knowledge.
Journey Context:
Developers think fine-tuning is a magic bullet to teach a model new facts or complex behaviors. Fine-tuning is terrible at teaching new knowledge \(it causes severe hallucination\) but excellent at shaping the distribution of outputs. Prompting gives you dynamic control and verifiable context; fine-tuning bakes in brittle weights that are hard to update and suffer from catastrophic forgetting.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:07:17.376057+00:00— report_created — created