Of course, my answer will be different than yours, but I would have continued the Progressive-era legislation from the pre-WWI era. Before WWI, America regulated the meat-packing industry, pharmaceuticals, and ended child labor. America established national parks and ended several major monopolies. America was attempting Prohibition, but that law was filled with problems before it left the halls of Congress--it was never meant to succeed. After WWI, America voted in presidents such as Harding and Hoover--presidents who would have been more at home during the Gilded Age when we expected less of our presidents. While it is dangerous to think of history as being filled with "what-if" scenarios, it is interesting to think about what would have happened if the Progressive Era would have continued past WWI. America could have regulated the rampant speculation on Wall Street and put in a minimum wage for its most vulnerable workers. America could have also provided for the elderly. America did all of this anyway through the New Deal programs, but perhaps the nation would not have had to suffer a Great Depression which spread throughout the world and led to the rise of totalitarian governments in Italy, Germany, and Japan.
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