Mr. Otis is not very worried about the ghost, though he does come to believe it exists. At first, in practical American fashion, he pooh-poohs the idea that ghosts could be real. After he realizes the ghost is real, his chief worry is about how to remove the blood stain that it leaves on the library floor. Despite the family's repeated applications of Paragon detergent to scrub it out, the stain keeps reappearing. Another worry Mr. Otis has is that the ghost's chains make so much noise. For that reason, Mr. Otis gives the ghost a bottle of Tammany Rising Sun Lubricator. Mr. Otis, along with the rest of the Otis family, creates a problem for the ghost: Mr. Otis is not afraid of him at all and focuses on scrubbing out his stains and asking him to oil his chains rather than reacting to him with fear.
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