Shirley Jackson's "The Lottery" is meant to demonstrate the negative impacts of blindly following "tradition" and avoiding societal change. In the story, the lottery is a traditional event that occurs every year on June 27th. The lottery has been an annual event since the first settlers arrived in the town long ago. Although a few things have changed slightly throughout the years, the townspeople refuse to completely change the lottery or to get rid of it entirely. The most likely reason for their hesitation to end the lottery is that they believe canceling the lottery will cause them to have poor crop growth during the coming season. Jackson does not make the reasoning explicit, but the likelihood of this reasoning can be inferred from statements she has placed throughout the story. As the townspeople discuss nearby towns who have cancelled the lottery entirely, Old Man Warner refers to their decision as foolish and states that there used to be a saying, "Lottery in June, corn be heavy soon." Old man Warner then goes on to say, "First thing you know, we'd all be eating stewed chickweed and acorns." Human sacrifices in return for a good crop yield have been prevalent throughout history, especially in the Aztec culture. It is highly likely that the town does not want to alter or get rid of the lottery for fear that without the annual sacrifice they will have a poor crop yield.
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