It only makes sense if it was checking for it being daytime (i.e. after sunrise and before sunset) which you cannot do in cron, rather than check for a specific hour.
Even then, using an LLM is about the stupidest way imaginable to do it since it’s not as if “when is it sunrise/sunset at a specific latitude and longitude and day of the year” can’t just be calculated with a formula or looked up in a table of values - its not as if the sunrise and sunset hours given latitude, longitude and day of the year change from year to year.
It just makes the design more complex (there’s at least one extra nasty corner case I can think of) and generally doesn’t add that much a performance improvement vs “run every 30 minutes”, to be worth it, IMHO.
It only makes sense if it was checking for it being daytime (i.e. after sunrise and before sunset) which you cannot do in cron, rather than check for a specific hour.
Even then, using an LLM is about the stupidest way imaginable to do it since it’s not as if “when is it sunrise/sunset at a specific latitude and longitude and day of the year” can’t just be calculated with a formula or looked up in a table of values - its not as if the sunrise and sunset hours given latitude, longitude and day of the year change from year to year.
It’s just astonishing how many thoroughly solved software problems are now being delegated to LLMs.
It shows a fundamental misunderstanding/delusion about what an LLM actually is.
It’s like people are trying to outsource the “figure things out” part of the process to the automated parrot which is the LLM.
Couldn’t you make whatever script your cron job runs also adjust the timing of the cron job to move with the sunrise / sunset?
You could.
It just makes the design more complex (there’s at least one extra nasty corner case I can think of) and generally doesn’t add that much a performance improvement vs “run every 30 minutes”, to be worth it, IMHO.