No side was really solely responsible for ending Reconstruction in the United States, but it was certainly the case that Southern Democrats, known as "Redeemers," had pushed for an end to Congressional Reconstruction for some time when it was finally brought to a close (by getting rid of the few remaining federal troops and military governors in the South) in 1877. This process had really begun in the early 1870s, as some states had already been returned to the control of the Democratic Party. This occurred because powerful politicians were able to forge alliances between poor whites and some business leaders, and it always had the support of secret organizations like "rifle clubs" and the infamous Ku Klux Klan, who aided in suppressing black voters. By 1877, when a political compromise ended Reconstruction in exchange for effective Southern acquiescence in the election of Republican candidate Rutherford B. Hayes, these "redeemers" were already in control of most of the former Confederacy. So Democrats were mostly responsible for bringing Reconstruction to an end. But they did so with the acceptance of many northern Republicans, who lacked the political will to continue Reconstruction in the face of flagging public interest.
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