Since 5:45 we're ~~sh~~flooding back!

Guys, come quick!!!! I found the cliff!!!!!

Imagine sexting smelling like fish...

 assert triangleObject.shouldFitInHole(triangleHole) == true

assert triangleObject.shouldFitInHole(squareHole) == false

Randomly rearranging non working code one doesn’t understand… sometimes gets working code, sometimes doesn’t fix the bug, sometimes it won’t even compile anymore? Has no clue what the problem is and only solves it randomly by accident?

Sounds like the LLM is as capable as me /s

Even then, the CT roughly indicates the amount of virus that was in the sample - which correlates with how infectious you are. But it also depends on the quality of the sample and how it was taken. If you're highly infectious but the slab was not correctly inserted, you might have less virus on your sample as one would expect and appear less infectious.

The original, or the metal version?

That must be one of the if not THE most American headline out there!

Technically correct, but back, when Reddit allowed 3rd party apps, I did get the occasional "Hey you lost something" comment, as some apps had a broken markdown rendered that wouldn't display it without.

Also it can have side effects if you use an underscore in the same paragraph or use it twice in a row, as it then suddenly can render as italic.

¯\_(ツ)/¯ Not sure how Lemmy reacts, though ¯\_(ツ)/¯

Although I know this, I cannot remember where I need to escape. So I just have two custom autocorrections: shrug which yields the regular (and broken on Lemmy) ¯_(ツ)_/¯ for general use and shrugmd with the markdown variant for the use on e.g. Lemmy: ¯\_(ツ)_/¯

In the end it's:

    shrug: ¯\_(ツ)_/¯ 
    shrugmd: ¯\\\_(ツ)\_/¯ 

Rule 34 in action

because it won't let you do that:

elvith@testvm:~$ sudo rm -fr /

rm: it is dangerous to operate recursively on '/'

rm: use --no-preserve-root to override this failsafe