The title of "Lamb to the Slaughter" is rather ingenious because it has so many possible meanings. "Lamb to the Slaughter" is more than a double-entendre; it might be called a "quadruple-entendre." A frozen leg of lamb is used by Mary Maloney to "slaughter" her husband. That weapon once belonged to a real lamb that was "slaughtered" in order to be used as food. Patrick is the one who is "slaughtered" in the story. He is an easy victim of his enraged wife because, like a lamb going to the slaughter, he is completely unsuspecting. Mary, who does the slaughtering in the story, behaves very much like a meek lamb until her husband shatters her illusions by telling her that he wants out of their marriage. The police who arrive on the scene do not suspect Mary because they have always considered her a very meek, mild, gentle, patient woman, not unlike a lamb. The whole story is based on the fact that the murder weapon is never found because no one would ever think of a murderer using a frozen leg of lamb for the "slaughter."
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