A major theme of David Foster Wallace's short story "Good People" is the tension between personal morality and practical decisions, and the resulting fear of hypocrisy. The story revolves around the relationship between two young Christians facing an unwanted pregnancy and contemplating the possibility of abortion, which their religious beliefs forbid. 19-year-old Lane feels the stress of the desire to maintain a positive relationship with God along with the fear of going to hell, and the necessity of abortion to allow him and his girlfriend Sheri to avoid shame and pursue the futures they planned for. Much of the story is told through Lane's contemplation: of Sheri, her plans to be a nurse, whether or not he loves her, and whether his relationship with her will result in him going to hell. He concludes that either decision they make, keeping a child out of wedlock or having an abortion, would go against their religious morality. The story ends without stating whether or not Sheri ends up having the abortion, instead finishing by examining Lane's fear and uncertainty. Ultimately the story conveys the tension between religious morality and the necessity of making decisions in life that oppose it, and examines the thought processes of a young couple trying to decide which choice they will make in opposition to their own morals.
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