I think that’s canonically true for Goku and Hulk

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

That’s why the cat is smug. It knows you know this.

I am very confused by your comment. Are you saying Putin never said that, or are you saying he was lying?

From Putin’s actual mouth:

ON DECISION TO LAUNCH ‘SPECIAL MILITARY OPERATION’

“We saw military infrastructure being ramped up, hundreds of military advisers working and regular deliveries of modern weapons from NATO. (The level of) danger was increasing every day. Russia preventively rebuffed the aggressor. It was necessary, timely and … right. The decision of a sovereign, strong, independent country.”

Just to be clear, he definitely said that, but he was definitely lying.

(source: https://www.reuters.com/world/europe/putin-speaks-victory-day-parade-moscows-red-square-2022-05-09/)

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.

The P in Prod stands for “It’ll be Pfine”

That guy was definitely a time traveler.

Oh absolutely! That guy does ‘barely contained psycho’ incredibly well!

In the show he was a sociopath with mind control powers, which if you know what he’s capable of (as JJ did), could be fairly intimidating.

David Tennant, not so much 😆 (Although he was terrific in that role)

they can keep my 42 cents and just stop their shit