Skip to main content

What techniques does Desai use to develop Ravi in "Games at Twilight"?

Anita Desai uses a combination of direct and indirect characterization to develop Ravi.  


There is quite a bit of direct characterization happening with Ravi in this story. Readers are told many specifics about his build and his thoughts. For example, we are told that Ravi is short when Desai talks about his short legs being the cause of his slow running ability.  


Desai uses indirect characterization early on for Ravi as well. Probably my favorite line about him is the following line.  



Ravi heard the whistling and picked his nose in a panic, trying to find comfort by burrowing the finger deep—deep into that soft tunnel.



Readers are specifically told that Ravi is in a panic and picking his nose to find comfort, but within that sentence is a lot of other information about Ravi. He's not a very confident kid. The kids are playing hide-and-seek, yet Ravi is terrified. He also finds comfort in picking his nose. This tells readers that Ravi is likely that "weird" kid who still picks his nose at an entirely too-old age. He's probably not well-liked, and he doesn't have a lot of friends. Those suspicions are confirmed by the end of the story when readers see that nobody is willing to admit that Ravi won the game. In fact, nobody even remembers that Ravi was playing at all.

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