The video provides a clear and pragmatic roadmap for AI implementation, effectively demystifying the trade-offs between RAG and fine-tuning. While it lacks deep technical novelty, it serves as an excellent reality check for organizations navigating the hype of LLM customization.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Is Fine-Tuning Still Needed? LLMs, RAG, & LoRA
Added:Is fine-tuning large language models still needed today?
Well let's take a well-known legal AI company because back in 2023 they fine- tuned their own model, their own custom AI, in partnership with the Frontier Lab, and in blind tests attorneys preferred this fine-tune model over the Frontier model at the time, which was GPT-4.
They preferred it 97% of the time.
A win for fine tuning.
They built a custom AI that lawyers actually preferred over the off the shelf leading model.
So the lesson is, if a general purpose model isn't quite right for some specific use case like legal work, then fine tune it.
Right?
Well, first let's define what fine tuning actually is.
So we're going to start off with a base model, a base LLM.
This is what comes off the shelf.
So this is either working with a Frontier lab directly or maybe picking out an open source model.
Now the base model is trained on a massive chunk of data.
Effectively we're kind of scraping information off the internet.
And using it to train that base model so there's lots of general knowledge that's going to be baked into the weights of the model.
Now fine tuning takes that base model and it customizes it how by continuing its training, but now it's doing it on a much more focused data set so we've just got some specific documents here which are really focused in one particular area.
So it might be legal contracts or maybe a an organization's internal support tickets, just like stuff that's not sitting around on the internet waiting to be scraped by base models.
And then what this results in is we get a new model out of this, a fine-tuned model, and that fine-tuned model incorporates, well, the information from the focus data set plus all of the weights from the base model as well.
They're now adjusted with that additional data.
So this resulting model should get better at certain narrow tasks.
That is the wonder of fine tuning.
But in practice how well does it work?
Well let's go back to this legal AI company.
So, in 2025, they created their own legal benchmark.
So benchmark would measure how effective their models were.
At performing particular tasks and they tested their find tune system against the latest crop of Frontier AI models.
So we've got the custom model here and then we've a bunch of Frontier AI models as well, kind of the mess general purpose models available at the time.
Now what was the result of this benchmark?
Well the result was that seven of the general purpose models.
Had now surpassed the company's custom model in the benchmark.
So this was by models that had never actually received any custom legal fine tuning, but they were still better.
And Bloomberg saw something similar to this.
They famously trained BloombergGPT from scratch and later evaluations found GPT-4 and ChatGPT outperforming Bloomberg GPT on many financial benchmarks.
So where does that leave fine-tuning today?
Is all that custom training worth doing when big frontier general models keep getting smarter on their own?
Well to answer that I think it's worth considering how general models have in many cases caught up to custom trained ones.
There's a few reasons for that and one it's just context windows have got really really big.
So the original GPT-3 that used a token window of 2k, 2000 tokens, and today Frontier models they routinely handle much much more than that, like 1 million tokens plus of input.
So if a if a model can read say 500 pages of legal documents directly in its prompt, then why bake those documents into the weights at all?
Just pass the stuff that's contextually relevant when prompting.
Now, second is reasoning models.
They do extended thinking inference time working through a problem step by step before answering.
So reasoning is coming from how hard the model thinks at the moment of the question at inference time rather than just from how it was trained months earlier.
And then third is just cheaper inference, as in models are getting more efficient and smarter.
So when the frontier model is constantly getting smarter and cheaper, training a custom version becomes a bit of a moving target, where by the time the fine tune model ships well the next frontier release may have leapfrogged it already.
Okay so so general models have got better but if we're not adjusting weight..how do we make a general model behave like a specialist? Like a legal scholar for example.
Well it turns out there is a whole stack of customization techniques that don't touch the model weights at all.
And the first of those is RAG, retrieval augmented generation.
Instead of training the documents into the model the application retrieves, that's the R in RAG, retrieves the documents at query time and then feeds them into the prompt.
There is also the consideration of context, specifically context engineering.
And the idea is that a good prompt is a carefully assembled bundle of context.
The system prompt, the relevant data, maybe some format guidelines and the like, they're all kind of packaged together.
And, the third thing I think we need to consider are agent skills.
These MD files that you can create.
So skills are folders of files that package up procedural knowledge, basically... How to do something and the tools to use to do it and the model loads them on demand when it sees a task back cause for them.
So instead of fine-tuning a model to know how to write SQL queries against a very specific schema, a SQL agent skill can tell the model exactly what to do and any general purpose model can use that skill.
So essentially what I'm trying to say is fine tuning isn't the only path to customization.
There's a whole stack of options that work without ever actually touching model weights.
Which is a good thing because fine tuning is not free.
In addition to the training run itself there's a cost in collecting the examples, and evaluating results, and avoiding regressions, and there's a cost of maintaining the custom models as the frontier models move on.
So all of this really begs the question.
Does anyone still need to fine tune at all?
Well, yes, but just for a much narrower set of reasons than back in 2023.
Now there is a modern technique called LoRa, that's low rank adaptation, that lets a team fine tune by training a small adapter, and this adapter sits on top of an existing base model.
So we've got the base model with its weights and then this adapter that sits on top of it.
So most of the original weights are staying locked, and then really a lot of what gets labeled as fine tuning in production today is some flavor of LoRa or a related parameter efficient method.
And fine tuning does still make sense in certain situations.
Well, like for example, when we are concerned about reduced latency if that's super important.
If a model has to respond in real time like a like a voice agent answering a phone call, well frontier reasoning models with all their thinking time are often too slow.
So if real-time responsiveness is the constraint, small fine-tuned models might still be the way to go.
Another reason is because of distillation.
Now the idea is to take a huge front-end model.
Generate high quality outputs from it then fine-tune a much smaller model on those outputs.
So you're essentially generating reasoning traces from a large parameter teacher model and using that to fine- tune smaller models.
And there's also reinforcement fine-tuning, RFT.
So instead of training only on fixed correct answers, RFT uses a prompt data set plus a grader and the model samples candidate answers, the grader scores those answers and training updates the model to make high scoring answers more likely.
Of course, the catch is that RFT only really works when the output can be programmatically graded, which is to say when there's a definitive right answer.
So..so fine tuning isn't dead.
From a practical decision framework today I think of it as the order going something like this.
So start with a base model and then you can implement prompt and context engineering.
If knowledge is fresh or proprietary well you might want to add in capabilities for RAG as well, and if procedural know-how is the thing that's missing... Well then at that point you might want to add in agent skills.
And then maybe only reach for the fine tuning if there's a specific bottleneck that the rest of this stack can't solve.
But what do you think?
Does fine tuning still have its place?
Let me know in the comments.
Related Videos

Expanding Stikbot thumbnails
leopoldshorts
2K views•2023-09-24

Digital Discrimination: Cognitive Bias in Machine Learning
redmonktechevents2974
4K views•2019-12-18

Evolutionary Approach to Clustering by Ujjwal Maulik
ICTStalks
279 views•2019-06-26

Rose Yu "Learning from Large-Scale Spatiotemporal Data"
networkscienceinstitute
2K views•2019-03-04

Stanford Seminar - Generalization through Task Representations with Foundation Models
stanfordonline
4K views•2025-07-14

Satellite-Based Wheat Yield Forecasting using GEE & Transformer Neural Network
gisrsinstitute
634 views•2025-06-15

Paradigm Shifts in Data Processing for the Generative AI Era: Robert Nishihara of Anyscale & Ray.io
GradientFlow
2K views•2025-01-02

How to Build Your Own GenAI-Based Knowledge Management System
2150GmbH
360 views•2025-06-03
Trending

YouTube Disabled Our Comments Again (Are Any Humans Left at YouTube?)
SpecialBooksbySpecialKids
39K views•2026-07-21

One Must Imagine Sisyphus Happy
vlogbrothers
61K views•2026-07-21

Future of Taylor Farms
maighstirtarot5385
11K views•2026-07-21

The Downfall of OnePlus!
techwiser
65K views•2026-07-21