In the first two paragraphs of "The Cask of Amontillado," readers learn that Montresor feels that he has been treated poorly by Fortunato a "thousand" times, but that something else has recently happened that is so significant that he can't let it go. As Montresor narrates, he tells the reader that he did not threaten Fortunato, but that he decided that he would inflict harm on him, and that he would do it in a way to make Fortunato would know it was him, Montresor, doing it--and why. Montresor's plan is to exact his revenge without putting himself at any risk of being found out or punished, because if he were caught, the revenge would be compromised. He smiles at the thought of what he will do to Fortunato.
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