I have to be honest. While this is obviously a smart and useful idea, it misses one of the core features of Jev: its confidence scores. Partial confidence could easily be mapped to fractional spaces, using unicode characters like U+2009: THIN SPACE. As it stands, this package is not harnessing the full power of Jev.
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.
Instead of using Choice with criteria "space_0", "space_1"..., it could be even more elegant to use criteria names like "", " "... which could be directly inserted into response.
> This means the package can add between 0 and 10 spaces. If more than 10 spaces are needed, Jev has no correct option. Which feels appropriate for this project.
I'll raise a PR which uses Jev to check if the target length is beyond this range
i maintained a system where for .. reasons (like other systems) from early days have users with id: null "null" "" and some i do not even know how to write here
> Please don't use this in production. Or anything important.
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.
Jev is a new type of model that just makes decisions based on given options. It's small and really really fast.
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.
Uses JEV to do something that's one line of code. Also, "leftpad" was a useless package from years ago that many important packages used instead of writing the code themselves. Its outage at some point broke a lot of packages.
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.
[0] https://docs.typesafe.ai/confidence
It works great, but maybe your implementation could save me some money. I’ll test it and report back.
https://joelgrus.com/2016/05/23/fizz-buzz-in-tensorflow/
You pad the text.
Oh, my god.
I'll raise a PR which uses Jev to check if the target length is beyond this range
Would have been funnier if it used the GLWTPL: https://spdx.org/licenses/GLWTPL.html
so probably early bird
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: