Recruitment is now basically Dead Internet theory...
RonSijm
joined 2 years ago
It gives an example:
For example, with the phrase “My favorite tropical fruits are __.” The LLM might start completing the sentence with the tokens “mango,” “lychee,” “papaya,” or “durian,” and each token is given a probability score. When there’s a range of different tokens to choose from, SynthID can adjust the probability score of each predicted token, in cases where it won’t compromise the quality, accuracy and creativity of the output.
So I suppose with a larger text, if all lists of things are "LLM Sorted", it's an indicator.
That's probably not the only thing, if it can detect a bunch of these indicators, there's a higher likelihood it's LLM text
Should I create functions/methods for packages/libraries that allow optional parameters to accept null as a value?
Having to pass in null values seems a bit weird. You can define functions and optional parameters like this:
function myFunction(a = 1, b = 1, c = null, d = null, e = true) {
return a * b;
}
Then people don't have to call your function with
myLibrary.myFunction(1, 7, null, null, true);
they just call your library with
myLibrary.myFunction(1, 7);
You could add a default inside the method signature, like:
function myFunction(a = 1, b = 1, c = null, d = null, e = true) {
if (c === null) {
c = 5;
}
return a * b * c;
}
because if you define it in the method:
function myFunction(a = 1, b = 1, c = 5, d = null, e = true) {
return a * b * c;
}
then if people still call it with
console.log(myFunction(5, 2, null));
Then the default c = 5 is overwritten by null, and results in 0.
I don't know if you really need to handle all that though, instead of just doing c = 5 - if people intentionally call your library with null, and things go wrong...? well yea ok, don't do that then.
But it depends on the use-case. If this is some method deep within a library, and some other calling method might be unintentionally dumping null into it, you could default it inside the method, and handle it
The ongoing feud between Wordpress and WP Engine is threatening open-source principles and good name
Since others already suggested mostly on-topic suggests, here's an alternative suggestion:
Instead of looking specifically for a mentor - look for an open source project that you can help with. Ideally one with a discord or something to it's easy to be in contact the the lead dev. A lot people don't mind mentoring juniors, but in my experience it doesn't happens that explicitly - "be my mentor" - and it might sound like you're asking them a lot.
If you invert it into "Hey I wanna help you with your open-source project, but I don't really know what to do, what your expectations are, how to implement a specific feature" - then you're offering to do work them, instead of asking for something. And implicitly you'll get mentorship in return.
And "real" projects probably also look better on your github / portfolio than only some dummy projects for learning purposes
The JetBrains Developer Recognition Program is expanding! Recognized #GitHub Stars can now enjoy free access to all JetBrains IDEs.
Sorry to be skeptical - but does this really do anything? It's nice, I guess, but it mostly just seems like marketing.
They already had a program for Open-Source Projects and a program for Developer Recognition - And maybe some other programs that I've missed.
And if you check the Github Stars Profiles - it's just 76 people. A lot of whom I suspect would already quality through one of their other programs
There's a Python WASM runtime, if you really want to run python in a browser for some reason...
https://github.com/wasmerio/wasmer-python