Then he kept playing a market that was already fully decided, when the only step left was to resolve the outcome. I believe the relevant adage here is "You can't cheat an honest man."

With that said, any trades after a market has concluded but before it is officially resolved should be voided. The market should close at the end of the time window (or the time of the resolving announcement, if that's the relevant trigger point).

It sucks.

The code hides an exception behind an if-then-else that defaults to the most common state, which isn't caught until it breaks things for the 1% of users who don't have that state.

The new feature quietly breaks a feature not covered by the acceptance tests.

The documentation is four times as long and nobody who relies on it can read it.

And I'm stuck spending my time going over tickets with a fine-toothed comb, reviewing PRs, and mentoring contributors to prevent all of this garbage from ending up in the live code.

The courts can intervene later, but they can't un-bomb a hospital.

This is setting aside the obvious problem where governments will often set laws based on self-interest rather than morality, particularly when it comes to military conflict.

It's insanely compact for a 96% board.

Thanks to enhanced pitch tracking in the last few years, they can now display even more information. The Pittsburgh Pirates' first- and third-base ribbon boards show pitch speed, vertical and horizontal break, and IIRC even the name of the pitch (bucketed based on the speed and break characteristics). It's a really neat addition to have in real time.

Imagine how much less you would use text messages if they still had a per-message cost.

The obvious problem is what happens when operations become abnormal. ATC shouldn't be staffed for normal operations, because then abnormal operations lead to catastrophe. Welcome to last night: the weather is bad, which causes a plane to abort two takeoffs, which causes that plane to need emergency services. This increases the controller's workload beyond his capacity, so he accidentally clears the emergency vehicle to cross in front of a landing airplane, and they can't see the airplane because the weather is bad, so they follow the instruction and promptly get hit with an airplane.

When some bad weather can be the difference between "this is fine, one controller can handle it" and two dead pilots, you need to be staffed for bad weather.

It only works if you deploy it against someone lower-status than you. The tactic is largely irrelevant and can be seamlessly replaced with any of a number of other tactics as needed. It's just enforcement of power hierarchies.