My kids started getting into one piece, an Anime I admittedly never watched, so I watch it with them. I get the hype now, there have been several times we’ve torn through 8+ episodes in one sitting. Skip Intro makes it fly by.

Yeah they left a bit out:

https://www.etymonline.com/word/dollar

The three left-hand pictures all subverted the trope too. Umbridge has a black heart, Rizzo is the least innocent girl in that movie, and the ski mask women scene is from a montage of crimes in a fairly dark comedy.

If you’re worried about the veracity of the claims, I can assure you they’re true.

that’s amazing.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

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.

I see a dark room of shady, hoody-wearing, code-projected-on-their-faces, typing-on-two-keyboards-at-once 90’s movie style hackers. The tables are littered with empty energy drink cans and empty pill bottles.

A man walks in. Smoking a thin cigarette, covered in tattoos and dressed in the flashiest interpretation of “Yakuza Gangster” imaginable, he grunts with disgust and mutters something in Japanese as he throws the cigarette to the floor, grinding it into the carpet with his thousand dollar shoes.

Flipping on the lights with an angry flourish, he yells at the room to gather for standup.

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.

My Thinkpad collection scoffs at your presumptions.

No.

System D was/Is a philosophical debate.

Wayland vs X is a mortal attempting to summit Mt. Everest naked. Everyone is cheering Wayland on, no one believes it’ll succeed.

Even the X people are like “Honestly it’d be a relief if you pulled this off, we’re so tired, please end us”

Next logical step: put wings on this puppy and call it a TRANE.

It’s true, one does not simply log into Mordor.

😏 https://github.com/anomalyce/rice-cooker

old school: Forgotten Realms

More games of thrones-ey, but less so: Wheel of Time

Grand but well paced: Stormlight Archive (Brandon Sanderson)

scifi one-shot: Sea of Rust

If playing in a video game and being stuck there counts as isekai, then Dr Stone getting teleportated to a future stone age world counts as an Isekai, and Dr. Stone is excellent.

If you’re using an active thunderbolt cable, you wire has proprietary code in it.

Red hat is the free coffee you get in the office at IBM

ZFS is baked in by default and the os is rock solid stable. It follows the same philosophy as Debian really, only the most tried and tested code makes it into the os.