Gulliver and his Master Horse eventually come to the conclusion that Houyhnhnmland Yahoos are preferable to European Yahoos because, with Houyhnhnmland Yahoos, what you see is what you get. European Yahoos share all the same vicious and terrible qualities that the Houyhnhnmland Yahoos possess -- greed, lust, violence, a general lack of common sense or intelligence, and so forth -- however, the filthy and disgusting exteriors of Houyhnhnmland Yahoos match their terrible and unscrupulous exteriors. European Yahoos, on the other hand, try to hide their true, disgusting, natures under a facade of cleanliness and politeness. European Yahoos may look and smell and seem better than their Houyhnhnmland counterparts, but they are just as awful, and so their appearances are really deceiving. This makes Houyhnhnmland Yahoos better, in a sense, because they do not hide their natures in this way. As a European Yahoo, then, this makes Houyhnhnmland Yahoos better than Gulliver.
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