Gravyness

"I don't know" is the last thing I expected someone to say, everyone is so fuckin certain nowadays. Thank you for taking the effort to post that, I mean it. I've always felt insecure about most of my convictions because the environment I was raised in could not support mistakes, which was perfect for computer engineering: We can always test again when we get something wrong. People are clearly not like that (or so I learned). Thanks. Really.

I know my english could use some improvement and I will leave this first comment to clarify I am a Brazilian developer: My main language is Portuguese, but I've been a productive software engineer for over 3 consecutive years in companies with daily meetings and did a good job. All I am asking is what should we (software engineers) focus our effort on?

Just a note: the link for Staff Software Engineer for Distributed Systems is returning 404. Also, does the company considers Senior React Developers (Web) for the React Native role?

What a great experience applying, thanks for that! Its organized, easy to navigate, descriptions are clear and straight to the point, it even has got a nice design! Talk about raising the bar!

> This might be a case of a rabbit you do not want to chase.

I'm sure the researchers will all collectively realize this, if it were to be the case, and disregard their 12 year academic journey with their great salaries in favor of research into more important topics like world hunger, renewable energy, etc.

I'm so sure that the percentage of sureness is an imaginary, quantum-entangled value between -7 and 13 billion percent.

> You're just using power that could go towards training a better LLM.

What if I haven't found that special someone yet, the one that will help me raise the next better LLM? I think I already got like 40% of the dataset I find valuable, all I need is to find someone with the other 40% and we could go in a journey together to find the remaining 20%. Sounds like the adventure of a life time.

Yes, but you could negotiate a token with each user on startup and if someone starts abusing your service you can block that access (perhaps automatically) or know who it is by authenticating the user.

Run "ssh -T [email protected]" command.

It should error like this:

    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
    Someone could be eavesdropping on you right now (man-in-the-middle attack)!
    It is also possible that a host key has just been changed.
    The fingerprint for the RSA key sent by the remote host is
    SHA256:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczCvj3tD2s.
    Please contact your system administrator.

Note that the SHA256 present there matches perfectly the one github send. If you don't remember the very first time you connected to github you also had to accept the key. The warning above shows up because the server is saved as a different RSA, for the SSH client it seems that someone setup a server for github but has a different key, which could mean someone is trying to trick you into connecting into the wrong server. This could also mean that github changed their RSA key which is why they published this article.

Why doesn't torch use automated artifact generation? As in a virtual machine or a github actions that download dependencies and compile it when a new python version is released?

No, they are lost forever... Humm... Wait I have an idea:

Prompt: How can entropy be reversed?

Reply: There is no single answer to this question as entropy is a thermodynamic property and therefore its reversal depends on the specific system under consideration. In general, however, entropy can be reversed by either increasing the temperature of the system (thus increasing the average kinetic energy of the particles) or by decreasing the volume of the system (thus increasing the number of collisions between particles).

    npm install -g @kaluma/cli

    kaluma flash index.js

This installs kaluma, finds the connected device, uploads the code and runs it. Love this simplicity, sounds like it was made the right way. Is there any posts with benchmarks? Very interested about the timing limits of the event loop implementation such as setInterval(()=>{}, 1); and other cpu heavy stuff like math stuff and pin output change speed from javascript.