The answer to this question depends on how one defines the word "freedom." African-Americans in the South were free in the sense that they were no longer enslaved. Slavery was formally abolished by the Thirteenth Amendment at the end of the Civil War. One might also argue that African-American men, at least, enjoyed a measure of political freedom during part of Reconstruction as they gained the right to vote in most states. In many areas, African-American sheriffs, legislators, and other political officials were put in office. But the end of Reconstruction brought an end to large-scale political participation, as Southern states enacted poll taxes, literacy tests, and other measures intended to disfranchise African-Americans. They also experienced the rise of Jim Crow laws that rigidly segregated Southern society. But throughout Reconstruction, most African-American people never experienced freedom in the sense that many of them understood it. For many black men in particular, freedom meant land ownership and the ability to provide for one's own family. Reconstruction, through its failure (or unwillingness) to enact land reforms, never made this possible, and the majority of African-American families lived meager existences as sharecroppers. So "freedom" was a relative term.
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