There have been many stock market crashes in American history, but the highest profile crash occurred in October of 1929. The crash really began on Thursday, October 25, when the market suffered tremendous losses only to be stabilized by a coalition of investment bankers who pumped money into the market. On October 29, forever known as "Black Tuesday," the market completely collapsed, as losses spiraled out of control. Investors, fearing a larger economic downturn as the 1920s came to a close, engaged in a mass sellout that devolved into a panic. By the end of the day, the market had witnessed over 16 million shares traded (a record to that point), and experienced the modern equivalent of of over 300 billion dollars. The crash heralded (even if it didn't exactly cause) the outbreak of the Great Depression. It also served as a sobering end to the so-called "roaring" Twenties.
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