Processors might no longer get twice as fast every few years, but now we can use the power of servers to write software that runs even slower.
We can add caching so numbers that have been checked once can be quickly looked up from an inMemory database.
“Is this number even?”
“yes of no”
“Invalid Response, please answer with yes of no”
“yes of no”
"Invalid Response,…
“… yes or no…”
Lexicon origin of Seven of Nine identified
Why are you leaking your API key?
*OUR api key
“Thanks mate, now I can just use it too”
Rofl. I just imagine OP furiously updating LinkedIn with “AI Programmer”.
Don’t use OpenAI’s outdated tools. Also, don’t rely on prompt engineering to force the output to conform. Instead, use a local LLM and something like jsonformer or parserllm which can provably output well-formed/parseable text.
yes of no
Not even valid json but compiler doesn’t complain
Have to say, this is not the most convoluted way of testing a simple thing I’ve seen in my years, not by a long shot.
Key seems valid. I’ll check all the integers for you to see how accurate it is.
While you’re at it, also test
- one
- three fifty
- 69 nice
- 6.9
- 4,20
- null (it’s German for zero)
- pie (and pi)
- cake
- fruits
- One million three hundred (wonder if it gets confused by “one” and “three”)
Probably not a good idea to show your API key to everyone…
What do you mean? I just see asterisks.
I wonder if that key works…
It does.
Rip
