There were several instances when the Cold War between the United States and the Soviet Union almost became "hot." But most historians agree that the Cuban Missile Crisis of October 1962 was perhaps the most dangerous moment in the conflict, when both sides came the closest to nuclear war. The crisis, which lasted nearly two weeks, occurred when the Soviet Union under Nikita Khrushchev secretly sent nuclear missiles to the island of Cuba. These missiles gave the Soviets what was known as "first-strike" capability, because they could reach most of the east coast of the United States within five minutes, making a full nuclear response impossible. When American spy planes revealed the existence of the missiles to military leaders, President John F. Kennedy demanded that they be removed, and imposed a naval blockade, known as a "quarantine" for diplomatic reasons, on the island. Kennedy opted not to attack the island, which we know now would almost certainly have resulted in nuclear war. The crisis ended, and the missiles were removed, when the Americans secretly agreed to remove missiles from Turkey and pledged not to invade Cuba. But the world came very close to nuclear war in those tense thirteen days.
As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...
Comments
Post a Comment