Skip to main content

How does geography influence the way we live?

Geography has an incredible influence on how we live. The buildings we build, the food we grow, the clothing we wear, and the kinds of work we do are just a few ways in which geography matters.


A settlement near an ocean must take into account tides and sandy coastlines.  To build upon the sand often means providing support many feet below the sand.  You will also see many houses on stilts in coastal area, to let the tide come in under the house as opposed to in the house.  Different kinds of materials for roofing exist, depending upon climate.  Building materials vary.  In an area in which there is a great deal of clay soil, bricks are cheaper to make, and you will see more brick houses.  In an area that has many forests, you are likely to see more frame houses.


What food we grow is based upon geography. Some terrains are ideal for rice, others for wheat.  We cannot grow mangoes or pineapples where I live, but it is ideal for tomatoes and peppers.  The terrain, the rainfall, and the seasons all dictate what gets grown.


I remember getting on a plane to go to Hawaii and handing my mother my winter coat, telling her I wouldn't need it for my trip.  There is a reason those natives in warm island cultures dress the way they do and a reason we dress the way we do in the northeastern part of the United States.  That is geography, which includes climate.


What kinds of work people do are often dependent on geography.  We cannot fish in the ocean unless we are near it.  We cannot grow wheat if we live in a swamp.  We cannot mine for coal if there are no coal seams or be sherpas if there are no mountains.  Many of us today have jobs today that can be done in most parts of the world, but geography still has a powerful impact on many.


Our various cultures are strongly influenced by geography.  And that is one reason its study remains important.

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