this post was submitted on 16 Jun 2024
293 points (98.7% liked)
Asklemmy
43942 readers
589 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's one good use case for me: produce a bigload of trialcontent in no time for load testing new stuff. "Make 2000 yada yada with column x and z ...". Keeps testing fun and varied while lots of testdata and that it's all nonsense doesn't matter.
I've found that testing code or formulas with LLM is a 50/50 now. Very often replying "use function blabla() and such snd so" very detailed instructions while this suggested function just doesn't exist at all in certain language asked for... it's still something I'ld try if I'm very stuck tho, never know.
I've noticed this a lot too—especially for M. But even though it makes up a function, it sometimes inspires a more optimised idea/method that can be more flexible for future datasets.
But most times it starts to massacre things and disregard prompted parameters or even producing an identical suggestion immediately after being told not to, why not to, and reconfirming original parameters of the query.
Some times punching in the same prompts five times for five iterations produces completely different results, but one may be on the right track and I can code the rest. It helps to set it's personality first, so it's sharing ideas it's seen out there, rather than trying to please.
At the least, it's a big time saver. Gone are the days where I get a few days spare to work on solving a complex problem through trial and discovery, so it's an excellent tool for reducing testing time and speeding up the route to an optimised method.