In Plessy v. Ferguson (1896), the Supreme Court ruled that the doctrine of "separate but equal" was constitutional. That meant that racial segregation was legal in public places, including trains and other modes of transportation, schools, drinking fountains, and other public spaces. This doctrine meant that the United States, particularly in the south, maintained separate public accommodations and schools for African-American and white people. Though the schools that African-American children attended were supposed to be equal, they were in fact not equal. Instead, African-American children in the south attended schools with far fewer resources than white schools. The doctrine of separate but equal was not overturned until the 1954 Supreme Court case Brown v. Board of Education, in which the court ruled that separate but equal schools were inherently unequal (meaning that even if these schools had the same resources, the fact that there were some schools for white people and some for African-Americans created inequality).
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