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.
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 fo
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.
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.