I’m curious, whats the hardest part of building products using LLM in your opinion?
thanks you for your help
I’m curious, whats the hardest part of building products using LLM in your opinion?
thanks you for your help
What’s an “LLM product”?
Do you mean “products using LLM’s”?
yes, edited, thanks!
what do you think?
I think the amazing thing is that it’s easy enough that really any beginner can learn Python and be up and running querying LLMs in a short time, probably even without any prior programming experience. Perhaps the tricky part is knowing how to construct good clear grammar for prompts that you know the LLM will “comprehend” correctly.
These days it’s standing out from the crowds when even new toasters have LLMs embedded now! Okay, we’re not that far yet, but there’s a lot of competition these days.
What about you, @louis030195, what is the hardest part for you?
You can actually get an AI toaster
It’s $3500, because all the AI of course
I heard these are around that same price… you’d have to add the LLM tho lol
Hello, I’m FlamethrowerGPT, and I’m coming for yououuuuuuu!
lol
Oops I was wrong on the price… about 3x toaster price … on the bright side it can ALSO cook your steak? lol
ETA: Just had an idea… you could make a snow-melting business with it? haha
Lol, that a Unitree GO2, it cost’s around $1300, if they actually manage to sell any of those flamethrower bots I’d be impressed
Ooh… what if we had 10,000 of them? Imagine!
But… back to topic. Interested in your thoughts, @louis030195 !
The UI/UX man. It will always be a pain in the wrong places to make. Backend is taken care by python.
Good point. There’s standards for browsers/displays, but some refuse to follow them or go off on their own tangents still and it’s indeed hard to get something to look good across every device.
There’s a lot of great libraries out there to help with it, though.
So far We are liking Flask. Runs on jquery and javascript which is nice. The moment react and angular enter the game, they are painful to learn. I mean why do we not agree to a common language for UI. Why does it have to be a steep learning curve?
Got that. Probably spent 20x as much on Qt UI as on the API data operations in one project.
Hardest part is versioned AI models from a company that starts with “Open” that change in ability to follow instructions regularly.
Yeah that too. We spent like 2 days, figuring out the right OpenAI version, which would work, until we were informed about the version. Now we made it so abstracted and configurable that the assistant now spawns in seconds. Although it is in beta, we just don’t want breaking changes.