Jo's secret, as told to Laurie, is that she has submitted two stories to a local newspaper editor, and she must wait to hear if they have been accepted for publication until the following week. She would have preferred to keep this news a complete secret because she will be so disappointed if they are not accepted, and she did not want anyone else to share in the disappointment. She only tells Laurie because he knows something is up with her anyway, and because he promises to tell her a secret in return: he ends up divulging that Mr. Brooke, his tutor, has been keeping Meg's glove in his pocket for days. Jo, however, does not care for this secret because she does not relish the idea of Meg being "taken away" from her family. Jo wants everything to say just as it is.
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