597 karma · joined April 12, 2013
As for fat reserves, even fairly lean individuals can probably go a week or two without food without breaking down much muscle. 14 days at 2500 calories is merely 10 pounds of fat. Unless you are morbidly skinny, you should have 10-15 pounds of fat ready.
I'm sure you've seen or heard of this case study of the Scottish man who fasted 382 days [pdf]! Of course, he did it under medical supervision. But I think it's an important case of what CAN be accomplished.
[pdf]: https://pmj.bmj.com/content/postgradmedj/49/569/203.full.pdf
If you fast long enough, say 48 hours I think, your body enters a mode of "autophagy", which is highly beneficial. So there's that.
When you consider your glycogen reserves, carb vs fat metabolism, insulin, ghrelin and other hormones, you get a rather complex machine. And what's really frustrating is that you are technically correct, in a sense. Eat fewer calories than you burn and you will lose weight. But that simplification borders on the dangerous. What's missing is that your body is not some passive observer, but an active participant, trying its best to help you survive.
Your body is amazingly good at adjusting how much you burn. When you cut calories, say 500 a day, your body will tend to compensate by burning a little less by reducing its temperature, by reducing fidgeting, by reducing your mood even! You'd need to cut 500 calories ABOVE that difference. So you end up having to cut closer to 750-1000 calories per day to get the same effect. Whereas when you fast, your metabolism rather obnoxiously tends to rise.
It ends up being healthier (and much easier) to eat 3500 calories less in one go, rather than splitting the difference across 7 days.
[1] https://drive.google.com/open?id=1WPsVhtBQmdgQl25_evlGQ1mmTQ...
Let's look at the simplest D, that is D = d/dx. What function satisfies du/dx = ku? An exponential, of course, because functions of the type u = a^x have derivative u' = ka^x for some k. What'e the most fundamental such function? Well, it's the one where du/dx = u, i.e. k = 1. This is none other than the exponential function e^x with e as currently defined. Every other choice of a "fundamental" exponential function will run into a lot of inconveniences later on.
What about another example. Let's look at D = d^2/dx^2. It's simple enough. What functions satisfy d^2u/dx^2 = ku. It appears the solution depends on whether k > 0 or k < 0. If k > 0, we can show that the hyperbolic trigonometric functions do the trick, so we can rehash the discussion above. If k < 0, however, we get into the usual trigonometric functions, namely what we now know as sin(rx) and cos(rx) for some choice of r, since for both u'' = -r^2u and you can find r from there. Again which r is the most fundamental? r = 1 of course, and this leads to the usual trigonometric functions.
If you choose r to be something else, we'd have a problem as we'll no longer have the nice property that sin'(x) = cos'(x) and so on. Also, these two examples are really the same example since e^(ix) = cos(x) + i*sin(x).
As a side note that should really be the main note...aesthetic calls are very important in mathematics. No one likes scaling factors to their identities. We like using fewer symbols to talk about common concepts. If we could make e = 1 or pi = 1 without inserting the opposite problem of complicating almost every single identity in mathematics needlessly, we would have done it a long time ago.
I think the reason c = 1 works in physics is because you can change a few other constants around (usually to 1) and things works out well. I fail to see how we can do the same in mathematics where things need to work on many many different layers. Also, if you look at any "Natural units" systems, they all have pi in them. Why didn't they get rid of it? Because it's even more fundamental than c!
But what if we've put no effort into the task yet? Well, I think procrastination of this sort is modeled well by our experience (Victor Hugo was an experienced author by that point). If in the past we've done some tasks and they've taken significantly longer time and energy than we initially thought, even if we don't consciously remember, our bodies will in some sense. I think what's happening is that there is a payoff based on the difference between effort P and required effort P' to finish in the same time. When P - P' > 0, we feel superb. When P - P' < 0, we feel like quitting.
You'd think one's perception would be improved after writing a dozen books, but maybe that's part of the reason a person starts writing another book after the first. A little bit of forgetfulness. But the brain doesn't forget. So, internally, it knows. So we have procrastination.
---
Example 1: Losing 20 lbs. How hard should it be?! A good goal to aim for if you do everything right and want to have a sustainable weight loss is 1 lb/wk. But realistically, it ends up being closer to 0.5 lb/wk for most. Would you spend something like 6 months to a year losing 20 lbs? What if there were more pounds to be lost? Now, if you go into this optimistically and not know this, you might lose a few pounds quickly and feel good, but then utterly quit when the real hard times come. (This mirrors any project that is easy to start but hard to complete, like html parsing)
---
Example 2: You intuitively know that a phone call to your phone company can help you save some money on your phone bill, but whether consciously or not, you somehow remember that it will take you 1-2 hours and a lot of emotional energy. You put this phone call off until it causes you enough emotional pain on the daily that putting it off by another day is as bad as the phone call itself. (This is an example of not even starting a project due to the perceived pain)
This highlights another thing. You can accumulate a lot of pain procrastinating on this call, but it's only the day to day pain that seems to matter in this strange internal calculation, because past pain is discounted a lot.
---
Example 3: (A bit tongue in cheek but...) Sleep. Let's say you've had some difficulty falling asleep over the last week. You perceive it as something that takes half an hour of "effort" to fall asleep. Naturally, you procrastinate until that effort is low enough, but this usually leads to too little sleep in the end.
---
Is there actionable advice from this? Yes. The more real-life knowledge you have of yourself, your projects (both successful and dropped), the more realistic your estimates can be. If you then bump up your estimates based on how off you were about them in the past, maybe then you'll get a glimpse on how much real work it'll take. Would you still start that project?
Maybe you'll end up starting fewer projects but dropping fewer before the finish line.
Have you tried sleeping elsewhere? On a couch? What about sleeping in a semi-seated position? Would that work?
How's your weight? Does it go up or down?
Finally, if you are in bed for 30 minutes and you haven't fallen asleep, it's probably way better to either get up and do some stuff or to just accept that you won't be sleeping and just stay there and go through your imagination.