My favorite go to, one I’ve used twice in the same campaign and no one was the wiser, is to throw some ridiculous fight at the party out of nowhere, let them sweat it out for a round or two, and start dropping hints it isn’t what it seems.

I had them stumble across a black dragon in a cave as a lvl 1 party once. After scaring the shit out of them, for a round or two, someone “finally noticed” that the wings seemed to be made of tar covered cloth. Druid did a nature check and realized that’s not what a black dragon roar sounds like at all. Literally 5 kobolds in a dragon coat.

One time, I thought we had canceled but everyone pinged me about why I wasn’t logged in to roll20 yet (got my weeks mixed up). Luckily one other person did too, so I told the party I was going to puppet their character so they would level up too. I had that character betray the party by leading them to a trap. They defeated the player character (I used their actual character sheet to fight the party), for them to discover it was a doppelganger, and the trap was the diopleganger’s lair. they solved through a bunch of traps and random creatures from the diopleganger’s managerie of tortured -to-the-point-of-insanity minor monsters until they found the actual player character that (as they discovered) had been kidnapped the night before.

One other time l, over lockdowns, I had a friend miss a few months of sessions due to some serious and very depressing circumstances. He still wanted to continue once life had calmed down. We were doing an Avernus campaign, and I had been NPCing his character, but I told him to fast forward to his character to the current party level (about 6 levels) and not tell anyone he was going to rejoin the play sessions or log into roll20 until I gave him the go ahead. About 15 minutes in, the party is sailing down the river Styx when they see a damaged flying fortress crash landing, streaking by overhead. They hear a hellish scream and see a buck naked tiefling jumping out of the ship directly for their raft. At this point my friend logs into discord and yells “I WANT MY SHIT BACK YOU IMPOSTER BASTARD!”. combat began immediately whereupon he fought himself and regained all the loot the imposter had been carrying. The party had a hell of a good time that night, and he never did explain (in character) what hell actually happened to him.

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.

LOL same. It’s a tricksy little wizard.

A gravid clown, a grave situation.

This post is like drinking a French Malbec after it’s been used to deglaze a burnt pan, I love it.

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.

basically, the government has to approve sales.

https://www.state.gov/u-s-arms-sales-and-defense-trade/

I already know people who would marry their cell phone if it had a wet hole.

Using food as the analogy:

Food…Code

Kitchen…Dev Environment (IDE, PC, etc)

Serving…Deploying

ok good so far

When I’m done with code I’m not going to deploy yet I commit and store it on a branch in git.

When I’m done making food that I’m not going to serve yet, I store it in a fridge or pantry.

When I need external code, I grab it from GitHub. When I need ingredients, I grab them from the grocery store.

So I think Food Storage, is the closest analog to git. I have local storage (pantry, fridge) that I can use to store food I have acquired.

Which would mean the grocery store is the closest analogy, but not a restaurant. Or maybe a grocery store with a restaurant.

I actually haven’t seen it!

It’s sad they only made one episode of Halo. I’d have watched a whole series as good as e1.

Ah, ok so I’m broken and don’t have to worry.

I loved both those things.

I don’t want to set the world on fire.

But I will if they fuck this up.

Folding is stone age tech. We need a wrinkle-free laundry compressor/decompressor.

I’m using an app, so I would never have known, thanks! And sorry if I spoiled that :(

Green lantern rings are willpower right? I’d give it to Vegeta with a green lantern ring vs hulk with a red one.

it’s the cornmeal they use to keep it from sticking during prep

Pretty sure this is the plot to >!Get Out.!<

why even wear a shirt at that point?!