Skip to main content

What important events happen in Chapter 3 of Deadline by Chris Crutcher?

Chapter 3's most important events are Ben's two meetings with Marla, his resolution to try to hook up with Dallas, and his dreams about talking with Jesus. 


Here's a more detailed summary:


The chapter takes place in late August, as Ben is talking with his therapist Marla (who's specifically a psychiatric social worker) about his plans to participate in football.


He's witty and playful with her, but in his mind, he reconsiders his plan to not tell his family about how he's going to die soon. Ben feels frightened and unsure of himself, but he also feels curious about the whole situation. He considers how he might pack a lifetime's worth of experiences into a single year, and about how, in terms of other living creatures and the history of the world, a year of life is paradoxically both an amazing gift and something practically negligible.


Ben jokes with Marla about condensing his life into a single year, then asks her to reassure his doctor that he's fine and still doesn't want medical treatment. Ben asks for Marla's help in a romantic matter, too: he's desperate to hook up with Dallas Suzuki, his crush.


After the meeting with Marla, Ben attends football practice, which is as vigorous as ever. He heads home with his brother Cody in Ben's beloved pickup truck, and they chat happily about football.


In another meeting with Marla the following day, she tries to convince Ben to get medical treatment. He distracts her by saying he wants to discuss a dream he had about having conversations with Jesus, whom Ben calls "Hey-Soos." In the dreams, "Hey-Soos" and Ben talk about what Ben might do with his remaining life, but "Hey-Soos" doesn't make any suggestions or give Ben any particular instructions.

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