Doctor Strangelove - Doomsday Machine

If I understand correctly, one reason there seem to be so many results for zero-sum games is that they have defined solutions, whereas in other situations, a mathematically valid strategy is to be a jerk ("blow up the island") and attempt to take the lion's share[1] of the surplus for oneself. One of the early game theory papers considers two people with radios, parachuted onto a grid, who must rendezvous. It derives a theoretical strategy: broadcast one's location, then destroy one's radio, forcing the other player to do all the walking. Bonus clip: [this video] @ 3:42 whew, still there: [link] all OK, Boomers! @ 3:55 unlike the House of Windsor during '14-'18, Kongo-Müller didn't bother to change his name: [link] (esp. 53:40-56:15) Those who prefer their skulls virtual are advised to avoid 30:10-33:30 and instead regard [link] [1] [link]

> ... where this is not only possible, but the common case. Couldn't not read that in Peter Sellers' voice [this video] > ... to find a 630 lines long test "case" with 22 nondescript assertions along the way. This is where tech team managers are abrogating their responsibility and job. It's the job of the organization to set policy standards to outlaw things like this. It's the job of the developer to cut as many corners of those policies as possible to ship code ASAP. And it's the job of a tech team manager to set up a detailed but efficient process (code review sign offs!) that paper over the gap between the two in a sane way. ... none of which helps immediately with a legacy codebase that's @$&@'d, though.