Skip to main content

Based on The Scarlet Letter, do we assume that we should be without flaw or sin? Should we never show that we have made a mistake?

In the final chapter of the novel, "Conclusion," the narrator says that "in the view of Infinite Purity, we are sinners all alike."  Therefore, despite the fact that some people try to live without sin—and some others pretend to do so—as human beings, we are fundamentally flawed and incapable of perfection.  If we were perfect, we would be gods.  The narrator claims that we are all sinners, every one of us, and so we cannot ever be totally without sin or flaw in the eyes of God.


Further, the narrator says,



Among the many morals which press upon us from the poor minister's miserable experience, we put only this into a sentence: "Be true!  Be true!  Be true!  Show freely to the world, if not your worst, yet some trait whereby the worst may be inferred!"



In other words, more important than being sinless—which the narrator has already identified as an impossibility—the narrator claims that we should be honest about our sinfulness.  If we are all, at least, honest about our sinful natures (if not our specific sins), then perhaps we will be less likely to judge one another (as the Puritans in the story do) and the guilt we feel for our sins will not be allowed to eat away at us (as Dimmesdale's guilt done to him). 

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

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 ...

Is 'efficate' a word in English?

I routinely hear the word "efficate" being used. For example, "The most powerful way to efficate a change in the system is to participate." I do not find entries for this word in common English dictionaries, but I do not have an unabridged dictionary. I have checked the OED (I'm not sure if it is considered unabridged), and it has no entry for "efficate". It does have an entry for "efficiate", which is used in the same way. Wordnik has an entry for "efficate" with over 1800 hits, thus providing some evidence for the frequency of use. I personally like the word and find the meaning very clear and obvious when others use it. If it's not currently an "officially documented" word, perhaps its continued use will result in it being better documented.