I would normally put a thought in a narrative in quotation marks, but it becomes boring and stilted to continually write, thought Mary, or thought John. A thought normally would have a different person; e.g. "He wants to know where I was yesterday," would be the thought of the dialogue, "You want to know where I was yesterday." But in certain contexts the first example could be spoken dialogue as well. The context should give clarity, but in more complicated narrative, i.e. numerous speakers, it would not. Has anyone any hot tips for writing thoughts in dialogue.
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