The answer to this question is a matter of perspective. The Cold War came about due to the rivalry that emerged between the United States and the Soviet Union in the immediate aftermath of World War II. The biggest issue involved postwar Europe. When the Soviet Union essentially set up Soviet-style communist regimes in Eastern Europe, beginning with Poland, the United States saw it as aggression on par with that perpetrated by Adolf Hitler leading up to World War II. From a Soviet perspective, however, it was a necessary move to establish a buffer zone between the Russian frontier and Western Europe, especially Germany. The Soviets had suffered over 27 million deaths during World War II, and they wanted to secure their borders. Similarly, the Soviets viewed American attempts to establish a pro-western government in Germany, as well as the flooding of Western Europe with American loans and economic assistance as capitalist aggression, and feared they ultimately wanted to destabilize the Soviet regime itself. Perhaps it is best to simply say that the Cold War developed because the two major superpowers who were left standing at the end of World War II had irreconcilable interests which led them into a series of political (and nearly military) conflicts.
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