To What Degree Does One Need to Know an Author's Background to Understand and Appreciate a Novel?

Looking for background information on novels and their authors before reading is a question being discussed all over the world. Many people believe that different literary works do not rely on further investigation "talking for themselves", but the facts rely on background information to understand and understand each story perfectly about it. The very famous, critical, famous novel "Rye catcher" published by J. D. Salinger is no exception.

In order to begin understanding the relationship between the author and the work, my student must first recognize Mary Shelley's personal career complexity. Given the clear similarity of the situation described in Mary Shelley and her novels it is my view to see if the author's reality has the same validity and purpose as mentioned in a fictitious account I am a student. A fictitious person, this is very beneficial. Against nonfiction literature. More importantly, my students have their own effective experiences and stories about the relationship (or discontinuity) between my family's career and dynamics and my individuality and identity formation. This is not that their parents guarantee who they will be in the future (as my students soon pointed out).

When writing novels, authors need to understand their role deeply. The author must grow to understand who their roles are, how they act, what they like and dislikes, and how they think . I use the word "growth", but since it is difficult for a writer to fully understand the internal workings of a character at the beginning of a story, its role will evolve through the process of writing a story. Programmers are facing the same situation, but there are customers, not characters. You may think that you know the customers of your app from the beginning, but your understanding of that customer may change over time. Perhaps you may think that they will use your app in some way, but after some user testing, you notice that they are using it in an unexpected but still informative way Let's see.