Fine-tuning
Adapting an already-pretrained model to a task by continuing to train it on a smaller, higher-quality dataset. Pretraining teaches next-word prediction across a large corpus; fine-tuning moves the weights toward one job finetuning-explained-kdnuggets.
Two ways to do it
- Full fine-tuning — every parameter updates. Memory-hungry, and risks catastrophic forgetting: the model loses general ability while gaining the specific one.
- PEFT (parameter-efficient fine-tuning) — freeze the base weights, train a small set of new ones. LoRA and QLoRA (quantized base plus low-rank adapters) and prompt tuning are the named methods finetuning-explained-kdnuggets.
PEFT is what makes the memory claims in unsloth-amd-support possible: an 8 B model fine-tuned on consumer hardware is an adapter being trained, not the model.
The adapter can become an object in its own right. skillsmith takes a PEFT artifact — prefix-tuning weights — and treats it as data: an LLM reads existing prefix weights plus a text description and synthesizes new prefix weights for a target skill. In ordinary PEFT the adapter is something you train and load; there it is both an input and an output of another model. The reframing matters for this page because it points past “train one adapter per task” toward composing existing ones — an early, preprint-stage idea, held with the caveats on its own page.
Don’t reach for it first
The most useful line in the founding explainer is a caution against its own subject: better
prompting or retrieval may solve the problem without training anything, and the techniques combine
rather than compete finetuning-explained-kdnuggets. The retrieval branch of that fork is paged
in ../research-wiki as retrieval-augmented-generation.
Unresolved here: the corpus states the decision rule and gives no basis for applying it. Nothing in it says when prompting stops being enough: no task taxonomy, no data-volume threshold, no cost comparison. An open question for synthesis.
The limit case (2026-08-03). timesfm is what “don’t fine-tune first” looks like taken all the way: a pretrained forecaster meant to be used zero-shot on series it has never seen, in a field whose classical answer was to fit a fresh model per series. Adaptation isn’t skipped because it’s premature — the product claim is that it isn’t needed. Whether that holds against a per-series ARIMA is exactly the evidence time-series-forecasting says the corpus doesn’t have.
Adapters and precision — a live gotcha
Serving a LoRA adapter by merging it into the base weights (W + sAB) and subtracting it later to
resume training is not safe in BF16: rounding is not associative, so the base weights drift
across merge/de-merge cycles. Unsloth avoids the round trip entirely and serves through vLLM’s LoRA
path unsloth-amd-support. A numerical-precision constraint on the whole adapter workflow, not a
quirk of one framework.
Tooling
Hugging Face PEFT, TRL, Unsloth and Axolotl are the named implementations finetuning-explained-kdnuggets. Only unsloth is paged so far.
Related
unsloth · machine-learning · classical-ml-algorithms · timesfm · time-series-forecasting · finetuning-explained-kdnuggets · unsloth-amd-support · synthesis