It works great, but maybe your implementation could save me some money. I’ll test it and report back.
important to note that the "confidence" score is... maybe not what people think it is - kind of useless, and just a convenience step from the probabilities.
from the docs: "confidence is a statistic computed from the probability distribution the answer already gives you." [0] I actually encourage people to visit the docs because it has a specific page on this with a little applet to really make this clear.
I'll raise a PR which uses Jev to check if the target length is beyond this range
it('trusts Jev when it chooses the wrong amount', async () => {
answer('space_2');
await expect(leftPad('jev', 8)).resolves.toBe(' jev');
});Would have been funnier if it used the GLWTPL: https://spdx.org/licenses/GLWTPL.html
Btw, this model also has very tiny inherent bias: https://jev-bias-analysis.stupidlabs.lol/
I use it mainly to check whether this code fits the rules I defined, just a yes or no. But I'm not sure if that's the right way to use it.
5 to 10 years from now, after this has worked itself deep into the npm dependency chain, we'll be lamenting how Jev-Leftpad is causing outages in critical services.
Leftpad is a npm package that chooses if it should or shouldn't pad the left side of a string. It was famous for bringing down everyone's npm installs a few years ago.
This combination is a double joke. Put something stupid in something stupid.
Though, again, a yet another project for a yet another "AI" to make someone else more dependent on it...
Related:
https://en.wikipedia.org/wiki/Jev_(AI_model)
https://typesafe.ai/