If I didn't have to worry about my grandparents getting scammed because they were having 99.99% of it effectively filtered or warned about at one layer or another before it actually became a problem...can you imagine how much you could lower that type of fraud/abuse?
Exactly! Apple for instance already does this with some ML tasks that only run when your device is plugged in, I think it's a great compromise.
Some thermostats prioritize low-usage times, too.
I find there to be a giant gap in learning about this stuff between material that boils down to "use magic words and system prompts to improve results from one of the big models" and "how do LLMs work from first principles".
I still haven't found a great resource that covers this middle ground, which seems to me to be where a lot of the power of these approaches is going to reside.
Read papers, build institution, experiment.
That last part may be the most important.
My sense is that I have a much better grasp of the foundational material here, having read in depth books and papers about that, but still can't quite wrap my head around the question of how people are actually "operationalizing" this into useful software.
But to your point about experimentation, it might just be the kind of thing where there is no path to enlightenment besides working on a project and running into and overcoming all the hurdles along the way.
> Design your tasks to be repeatable and small steps, call the OpenAI API and log all requests/responses. > Filter out any bad responses and take a representative sample of the data you have collected from OpenAI,and train a Mistral or Llama2 model with the request/response pairs.
> Measure the quality of your model vs OpenAI for the same inputs, and then swap out the model in your workflow once happy with the results.
> This is how I made this model: Design your tasks to be repeatable and small steps, call the OpenAI API and log all requests/responses. > Filter out any bad responses and take a representative sample of the data you have collected from OpenAI,and train a Mistral or Llama2 model with the request/response pairs.
Just one example.
I've gone through a few of these "new kinds of software becoming useful" transition periods - most notably applications moving to the web, and then native smart phone applications - and in none of those transitions was there a dearth of resources on how to spin up on doing useful things due to this "moat" concern.
Nobody was protecting their iphone app dev moat by not publishing books and training courses on Objective-C and XCode...
Filter out any bad responses and take a representative sample of the data you have collected from OpenAI,and train a Mistral or Llama2 model with the request/response pairs.
Measure the quality of your model vs OpenAI for the same inputs, and then swap out the model in your workflow once happy with the results.
Getting a consistently good result for one shape of input may not indicate that same performance for another shape of input for example.
Anyway, nothing to say you can't use both, or have a fallback system.
I've run hundreds of millions (150m so far in a couple of weeks of non-continuous running as I tweaked things) of tokens through my 2x 3090 with a 13b llama2 model I fine tuned on tasks like: summary, knowledge graph generation, writing using the knowledge graph, grammar, spelling, and transcription correction, etc.
This type of stuff is going to be done at scale with a modest budget if you have the skills to tune more efficient and faster models to your use cases.