Fortunato offended Montresor numerous times in the past, and Montresor seeks revenge by burying him alive. After running into Fortunato, who had been drinking excessive amounts of wine throughout the night, Montresor invites him over to try some Amontillado, which is a very rare wine. Fortunato enthusiastically follows Montresor through his family's catacombs in order to try the Amontillado wine. While traveling through the catacombs, Fortunato continues to drink until he walks into a small room where Montresor shackles him. Fortunato is helpless and cannot escape as Montresor begins to build a wall out of stones until Fortunato's voice cannot be heard. Fortunato ends up dying behind the stone wall in the catacombs, and Montresor says he has been buried for fifty years.
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