Autonomous cars could allow space currently devoted to idle car storage to be reused for denser development patterns, which would reduce the need for car-based transport in the first place.
The paragraphs under the "Slowing Down" heading kind of imply that they think the argument also applies in an urban environment. It's incredibly frustrating and infuriating to read such an utterly anti-bike anti-walker policy get advocated like this.
Already starting to happening. I know a kid in high school who's annoyed by his parents insisting that he learns to drive. Some of that is because he believe the tech is going to get good enough by the time he gets out of college, the rest is because I've set an example that it's possible to achieve a car-free lifestyle already if you make it a major priority.
I agree they're the biggest nuisance, but.. they're just a nuisance. I'm not fearing for my life from bikes like I do from cars all the time at almost every intersection.
Most games shape their random events because true random is actually really frustrating to play.. but what it appears to me here is that there's a PRNG here that was seeded before he save-stated.. and since he didn't do anything that called the PRNG before that head-butt, the number didn't changed.
This sort of behavior is famous in Fire Emblem.. but there's also a trick due to how some of the games do pathfinding. Some of the games, if the game can't decide which path to take, calls the PRNG to decide. Since you've induced a call to the PRNG, you can redo a specific battle with a different random number generation.
Just because you don't explicitly write it down doesn't mean you didn't prove something. For optimization, you have to prove to yourself that the new code behaves equivalently to the old code. Anytime you use algebra you're doing a small proof to show that two expressions should be treated equivalently. Writing a proof down is the very last step, the hard part is thinking it through.
Actually, this method is one of the most efficient ways to multiply in software. It's called the "Comba" method in that context, and is efficient for multiplying 32x32 words or smaller, due to cache effects and function overhead required by more complicated algorithms. Over about 32 words on many architectures, the algorithmic advantage of the Karatsuba method wins out.