It can be hard to tell what an author's intention was in writing a particular text, but Hawthorne often returns to the same subjects again and again: religion, sin, and guilt. "Young Goodman Brown" doesn't seem to be an exception. Goodman Brown treats religious faith, symbolized by Faith, his wife, rather casually. Though Faith "sadly" asks him not to go into the forest that night, he insists that he must, and though she seems "melancholy" when he looks back at her, he continues on his path. He thinks to himself, "'after this one night, I'll cling to her skirts and follow her to Heaven.'" However, this is not how faith is supposed to work: one cannot simply lay it down and pick it up whenever it is convenient. Brown takes his faith, and Faith, for granted, assuming that they will be waiting for him, unchanged, whenever he is ready to return to them. In short, they aren't. Whether he actually sees Faith in the woods at the witches' Sabbath, or whether it was just a dream, his relationship with God and the world has been changed forever by his own faithless behavior. Therefore, I believe that Hawthorne may have intended this text to be a sort of meditation on faith, as it conveys the theme that real faith is something a believer always carries with them.
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