Even though his men want him to take some food and leave as soon as possible, Odysseus wants to stay in Polyphemus's cave because he hopes "[he] might see [the cave's owner] and [this owner] might offer [Odysseus] gifts." Odysseus might expect such gifts from an obviously wealthy host because of the ancient Greek ideas concerning hospitality. Greeks believed Zeus protected travelers and that a host had a religious obligation to offer hospitality to any traveler; this hospitality would often include the presentation of a guest-gift, if such a gift were financially viable for the host. Odysseus isn't just randomly expecting presents; rather, he's expecting (perhaps a tad arrogantly) that he will be offered gifts as an extension of this hospitality. The guest, however, also had an obligation not to take advantage of a host's hospitality, and so we might read Odysseus's expectation as a bit presumptuous.
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