Skip to main content

How long can a human survive in a drought?

The survival period for someone in a drought is really dependent upon their access to drinking water and, to some extent, food. Drought is the word we use to describe periods of abnormally low rainfall, as opposed to places which receive little rainfall as a normal part of weather patterns. Currently, several parts of the world are experiencing drought. The state of California, in the United States, is experiencing a drought, but because this is a developed area with the ability to drill for water and import drinking water from other locations, the people here are not in as immediate danger as they might be otherwise. The major downside to the California drought is that there is a deficit in the amount of water available for agriculture-- in other words, food production in California is at risk. 


As long as a person in a drought area has access to drinking water, they can survive indefinitely regardless of the drought. Without access to drinking water, a person will begin to experience dehydration. Symptoms of dehydration include sleepiness, thirst, decreased urine output, headache, dizziness, dry skin, and low blood pressure. Symptoms will get worse the longer someone goes without adequate hydration, and most doctors agree that if someone goes more than three days without water, they will die. There have been some reports of emergency situations where people have survived for more than a week without water, but this would still be severely detrimental to health.

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