After Robert E. Lee's troops were cut off from supplies and surrounded by the Union forces, surrender was inevitable. Lee's role in the surrender from this difficult position was to ask Ulysses S. Grant what the terms of surrender would be. For his part, Ulysses S. Grant wanted to begin the process of healing the nation at Appomattox. While a natural reaction would be to approach the surrender by gloating and punishing the South, Grant offered fairly lenient terms for the Army of Northern Virginia. He granted a full pardon to all of the soldiers and officers and even printed pardons for them to take back home with them. He allowed the officers to keep their sidearms, but all weapons of war were to be surrendered by the soldiers. The Union also fed the starving Confederate troops before sending them home to begin the process of rebuilding.
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