<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Week 14 - Fine-Tuning &amp; LLM Customization on AI Platform Engineering Handbook</title><link>/docs/week-14/</link><description>Recent content in Week 14 - Fine-Tuning &amp; LLM Customization on AI Platform Engineering Handbook</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2026 Harshhaa</copyright><atom:link href="/docs/week-14/index.xml" rel="self" type="application/rss+xml"/><item><title>Fine-Tuning Fundamentals</title><link>/docs/week-14/fine-tuning-fundamentals/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-14/fine-tuning-fundamentals/</guid><description>&lt;hr&gt;
&lt;h1 id="fine-tuning-fundamentals"&gt;Fine-Tuning Fundamentals&lt;/h1&gt;
&lt;h2 id="the-big-picture-first"&gt;The Big Picture First&lt;/h2&gt;
&lt;p&gt;Throughout almost this entire series, we&amp;rsquo;ve treated the underlying language model itself as a fixed, unchanging thing — something you connect to through an API, prompt cleverly, and build tools and RAG systems around, but never actually modify directly. Fine-tuning is about something genuinely different: actually changing the model itself, adjusting its own internal learned parameters, so that it behaves differently going forward, for every single future conversation, without needing to be specifically re-instructed each time through a prompt. Here&amp;rsquo;s the useful way to think about the relationship between prompting and fine-tuning: prompting is like giving someone very detailed, careful instructions right before they start a specific task — genuinely helpful, but it has to be repeated every single time. Fine-tuning is more like actually training and coaching that same person over time, so the new behavior becomes a genuinely natural, built-in part of how they approach things going forward, without needing to be told all over again each time. Let&amp;rsquo;s build up an understanding of how this actually works.&lt;/p&gt;</description></item><item><title>Human Feedback &amp; Alignment</title><link>/docs/week-14/human-feedback-alignment/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-14/human-feedback-alignment/</guid><description>&lt;hr&gt;
&lt;h1 id="human-feedback--alignment"&gt;Human Feedback &amp;amp; Alignment&lt;/h1&gt;
&lt;h2 id="the-big-picture-first"&gt;The Big Picture First&lt;/h2&gt;
&lt;p&gt;Everything we covered in the previous two Week 14 explanations focused on teaching a model new knowledge, new formats, or new domain-specific skills. This final section addresses a genuinely different, and arguably even more fundamental question: how do you actually teach a model to behave the way humans genuinely want it to behave, in the first place — to be genuinely helpful, honest, and safe, rather than simply being good at predicting statistically plausible-sounding text? This is precisely the gap that instruction tuning, which we touched on earlier, only partially closes. A model can be instruction-tuned to follow the general format of instructions, while still genuinely producing responses that are subtly unhelpful, misleading, or occasionally genuinely harmful. Alignment techniques — RLHF, DPO, and everything else covered in this section — are specifically about closing that remaining gap, using genuine human judgment about what &amp;ldquo;good&amp;rdquo; actually looks like, to further shape a model&amp;rsquo;s behavior in that particular direction. This is, in a very real sense, part of the same broader process that actually shaped how I, Claude, myself actually behave.&lt;/p&gt;</description></item><item><title>Parameter-Efficient Fine-Tuning (PEFT)</title><link>/docs/week-14/parameter-efficient-fine-tuning-peft/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-14/parameter-efficient-fine-tuning-peft/</guid><description>&lt;hr&gt;
&lt;h1 id="parameter-efficient-fine-tuning-peft"&gt;Parameter-Efficient Fine-Tuning (PEFT)&lt;/h1&gt;
&lt;h2 id="the-big-picture-first"&gt;The Big Picture First&lt;/h2&gt;
&lt;p&gt;At the very end of the previous explanation, we touched briefly on LoRA and parameter-efficient fine-tuning as a way to make fine-tuning more affordable. This whole section is dedicated entirely to unpacking that idea properly, because it turns out to be one of the single most practically important developments in making fine-tuning genuinely accessible to regular developers and smaller teams, rather than remaining something only the very largest, best-resourced companies could ever realistically afford to do. Here&amp;rsquo;s the core problem PEFT solves: a modern large language model can have many billions of individual internal parameters, and traditional &amp;ldquo;full fine-tuning&amp;rdquo; means updating every single one of them — which requires an enormous amount of GPU memory, not just to hold the model itself, but to hold all the additional bookkeeping information needed to actually calculate how each of those billions of parameters should change. PEFT is a whole family of clever techniques that dramatically reduce this requirement, making fine-tuning something that can genuinely be done on much more modest, affordable hardware. Let&amp;rsquo;s work through exactly how.&lt;/p&gt;</description></item></channel></rss>