I also think that what Jonas could not articulate is that there is a risk of loss in love. His life of emotional deprivation does not give him a vocabulary with which to express this idea, but the book makes clear that people are not really emotionally invested in one another in any way. If Jonas were to die, his parents, parental units, really, would no doubt miss him, but there is nothing to suggest they would feel grief. They are on record as not loving him. Death is unknown in this community, since it is euthanasia that is tidied up, euphemized, and hidden from the people. If one's beloved grandparent were to die, it would be a painful loss, one of the risks of love. Similarly, if people chose partners based on love, that love could be lost, another of its risks.
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 ...
way too long it should be shorter you want the people to understand it.
ReplyDelete