Skip to main content

What is John Green arguing in Paper Towns?

In Paper Towns, John Green is arguing that we often misinterpret other people and that identity (particularly in adolescence) is a fluid, ever-changing phenomenon in a person's life. 


This is quite apparent in the book with Quentin's changing ideas about Margo. In Quentin's mind, Margo continues to exist, much unchanged, as she did when they were children. The "love" that he feels for her is really love towards a perception he has of her that isn't real. Quentin realizes this at the end of the novel and gives up his relentless pursuit of her. 


This idea about the divide between reality and perception is further encapsulated in the title and one of the motifs throughout the book: paper towns. Paper towns are fake towns printed on maps to prevent plagiarism; they seem to exist when you are looking at the map but are, in fact, not real. However, that part of the map still exists; it's just that you won't find what you expected when you get there. 


Quentin spends the entire book chasing an idea of Margo that is constructed from his fantasy, and he ultimately chases her to a paper town. In doing so, he realizes that his idea of her is also a paper town. It exists in his personal "map" of the world but not in reality. 


In sum, John Green is arguing that our perceptions of others are subjective, and he is imploring us to look past the paper town we construct of someone and understand who they really are. Additionally, he is exploring the manner in which a person's identity is formed throughout adolescence. Quentin still imagines Margo as she existed when they were children. She is, in fact, an entirely different person now, one that he doesn't know at all. 


Key quotes:


“What a treacherous thing to believe that a person is more than a person.” 


“It is easy to forget how full the world is of people, full to bursting, and each of them imaginable and consistently misimagined.” 

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

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...