Skip to main content

In Hatchet, how does Brian know how many days he has been in the Canadian wilderness?

Brian marks the passage of time by making marks on a stone by his shelter each day. 


Brian ends up being in the wilderness for a long time.  He wants to mark the days, but that is all they are to him at that point—just days. 



The days had folded one into another and mixed so that after two or three weeks he only knew time had passed in days because he made a mark for each day in the stone near the door to his shelter. (Ch. 15) 



To Brian, events are more important.  Most days just pass with the sun going up and coming down, but there are some special occasions.  The day of “First Meat” is the day he finally figured out how to get meat.  He had been frustrated because the birds, which he called foolbirds, seemed so dumb, yet he could not get them. 



But in the end he found that if he saw the bird sitting and moved sideways toward it—not directly toward it but at an angle, back and forth—he could get close enough to put the spear point out ahead almost to the bird and thrust-lunge with it. (Ch. 15) 



Naturally getting meat was a milestone for Brian.  He did not have the survival kit yet. He was surviving on berries.  At home he could go to the store and buy a chicken.  It was not so easy on his own in the wilderness.  He was really proud of himself. 


Other milestones include First Arrow Day and First Rabbit Day.  The rabbits gave him variety in his diet.  He also learned to fish with a spear.  He definitely was healthier after that.  For a boy living on his own in the wild, Brian was doing a pretty good job.  It kept him alive until he was found by searchers.

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.