There is really no date for the end of the Cold War--some would put its end as 1989, when the communist governments of Eastern Europe collapsed, while others would choose 1991, when the Soviet Union ceased to exist. Whatever the date, the Cold War came to an end with the collapse of communism. This process occurred for a number of reasons. One was that the Soviet Union faced major economic hardships as it struggled to maintain its military power. The Soviet economy, it is often said, struggled to provide its people with both "guns and butter." Mikhail Gorbachev, the reform-minded Soviet leader who took power in 1985, sought to institute structural economic changes that were impossible to implement while spending so much money on the military. So he sought more normalized relations with the United States. He also encouraged a new policy of openness, "glasnost", in the USSR. When the countries of Eastern Europe, beginning with Poland, began to pursue similar reforms, many began to overthrow their Communist regimes. Gorbachev, unlike previous Soviet leaders, declined to intervene to stop these changes, and Communism quickly collapsed in almost every Eastern European country. In 1991, the Soviet Union itself fell apart, with the Baltic state of Lithuania declaring independence, and others demanding it. Gorbachev was removed from power, and the rise of Boris Yeltsin to the presidency of a new government spelled the end of the USSR. If it was not over already, the Cold War reached a definitive end in 1991.
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