3 ms·
Continuous fine tuning so you don't have to pass everything in the context with every query would definitely yield a better UX.
by esafak 3y ago
Continuous fine tuning so you don't have to pass everything in the context with every query would definitely yield a better UX.
- littlestymaar 3y agoAfaik the few-shots learning abilities of LLMs are much better than what you can achieve with fine tuning when you only have tiny samples. Of course it is true for real long context but it's not clear if its going to work with the sparse context hacks intended to keep memory size low. Having the ability to keep the same coding session forever without having the LLM forgetting all the time and making the same mistakes over and over would be a game changer.
- nl 3y agoI'd argue the fine-tuned UX is often worse. People like RAG-based solutions because you can include references in your answer very easily (eg, Perplexity, or see the DAnswer "internal search" product launched today on HN). That is extremely hard to make work reliably from a fine-tuned model.
- esafak 3y agoI mean UX from the perspective of the person doing the search, not the engineer. I don't dispute that fine tuning is harder to implement.
- nl 3y agoI mean from the perspective of the person doing the search too. They often want to see the reference - for example the LLM is constructing an answer about some company policy question it is good to include references to the actual company policy documents by URL. This is easy using RAG, but very hard to do reliably just using a fine tuned LLM. See Perplexity for a great example of this at web scale.
- esafak 3y agoThis is true. If LLMs recalled perfectly their purveyors would get into legal trouble :)