Interestingly enough, that's how Société Générale lost huge amounts of money following the discovery of Jerôme Kerviel's misbehavior. They recklessly closed their positions, shooting themselves in the foot in the process.
The usual solution for player elimination in online games is the ability to leave the game you've been eliminated from and start another game right away, which is embodied by matchmaking systems and solo queuing.
Doesn't help when you want to stick with a group of players (e.g. friends, team) and brings its own kind if issues.
The default presentation structure of PowerPoint makes it very easy to build bad bullet point presentations.
One could argue that means PowerPoint has bad default settings and thus is not a very good tool.
What's new? Well, if we keep replacing low-skill jobs by high-skills ones, we may have a little problem: are humans going to keep up with the training? Is the workforce going to adapt fast enough?
When job replacement happens over several generations, it's a pretty easy problem to solve. When it gets faster, turns out some human abilities are not scaling very well.
My main progamming language at the time is Java, and the amount of assistance my IDE provides is astonishing (to the surprise of no one, it's IntelliJ). The confidence strong automatic refactors provide is of great help when managing large codebases.
The issue here is handling portability yourself or let the language and its toolchain do it. The odds that you are doing a better job than the community to handle portability are pretty low right from the start and they get lower and lower if the laguage is well-supported.
My "ugly macros" are tested against my own implementation only. Compiler's are tested against thousands.