nxdefiant

I read this to the old Arby's commercial jingle

https://youtu.be/PiupfW_Qw6A

We only get a summary, not a transcript, but:

https://www.whitehouse.gov/briefing-room/statements-releases/2024/05/06/readout-of-president-joe-bidens-call-with-prime-minister-netanyahu-of-israel-5/

I think this speaks far more about Netanyahu than it does about Biden. I have no doubt he'd double down on the crazy if the U.S. unilaterally ceased support, even going so far as to threaten or use nukes. Menachem was under significant economic and political pressure in his own country at the time, Netanyahu isn't facing that yet. His own people will have to force his hand before a foreign leader can.

Also: https://www.cnn.com/2023/12/12/politics/biden-israel-losing-support-netanyahu/index.html

Imagine scrolling back in the Slack chat 50 years to find that one thing someone said about how the chip bypass worked.

or the hand anatomy of those girls.

Distributed Honor-system Clothes Peg Server

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I've only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn't be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn't have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it's nicer to work with a repo that keeps its focus tight.

It's comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

It's not uncommon to keep example bad data around for regression to run against, and I imagine that's not the only example in a compression library, but I'd definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.

AMR TIME!

LOL same. It's a tricksy little wizard.

I tried to get chatGPT to solve wordle for me once. The stupid thing can't keep more than half a rule straight at one time.

Bad picture for an article advocating communication and de escalation.The entire plot with Azula is that she's so incredibly inflexible and self absorbed that she cannot be reasoned with. Her character arc ends with her literally screaming in chains.

Ok, you got me pretty good with "horse fursona"