Many people in Salem are inclined to avoid Sunday mornings at the meetinghouse because they dislike the minister, Mr. Parris. John Proctor tells Mr. Hale that he doesn't see the "light of God" in Parris, and he has even avoided having his youngest son christened by Parris because he doesn't want the man to lay hands on his child. In addition to these concerns, Proctor says that it "hurt[s] [his] prayer" that Parris insisted on -- and evidently got -- golden candlesticks for the altar when there were already perfectly good pewter candlesticks that were handmade by Francis Nurse, a well-respected member of the Salem community. When Proctor sees those golden candlesticks gleaming at Parris's elbow when he preaches, it seems to make Proctor feel that Parris's priorities are out of line.
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