Skip to main content

WARNING about hiker food videos

I have been watching a number of hiker videos that discuss food, quantity, calories, supplements etc and most of them are, simply put, DANGEROUS. Whether you are hiking the PCT, CDT, AT, FT, Sea2Sea you need to know a lot more than what is in the guide books and you better start reading, watching, and testing before you head out onto the trail.

I received my copy of Andrew Skurka's Ultimate Hiker's Gear Guide; 2nd Ed. and there is a section on food. He confirms my calculation of about 1 pound per 1000 calories only he prefers ounces; and we are pretty close. Where we differ is that he recommends carrying between 2250 and 2750 calories per day without consideration for the amount of energy burned on the trail or that you WILL be running a deficit. Ge simply says that his number is a good number.

Further reading Andrew talked about pre-hike loading of fat and protein. There are some interesting calculations when it comes to measuring the distance to be traveled and calories needed and what that means in body fat. Here he is only hinting at running a deficit.

So here is the thing. None of the hiker food videos that I've watched make any such warning and they certainly do not go into the detail that Andrew does. And so after all of that... make sure you talk to your family doctor and get a checkup. Make sure the doctor knows what you are about to do.

Then make sure to read [a] the US Army Survival Guide and [b] Bushcraft 101. Know, understand and memorize the Rule of 3s; and The 5 Cs. While I want you know have some survival knowledge I expect that you'll never use it. The point is to avoid the potential of the situation long before it's ever a thought.

Be prepared without sacrificing fun.

For example I carry 3 types of water processing. [a] gravity filter [b] aquamira drops [c] aquamira tabs. The tabs go in my first aid kit. If something goes very wrong or someone else needs help the tabs are the first thing I'm willing to part with.

My Shelter is damage proof. If something should break then I can still make a shelter from the sum of the remaining parts.

Looping back about food; in this picture I have my smallest stove. It's a toaks 500ml cup with an esbit stove, 4 esbit tabs, toaks syphon stove, toaks folding spork, full sized lighter, and a windscreen. The thing is I have not heard anyone talk about resupply and sharing the items that are packaged badly. A box of esbit tabs is qty 16. On the other hand denatured alcohol is cheaper and more readily available. And it does not smell bad.

I just noticed that I can burn an esbit tab on my toaks syphon if I just turn it upside down.

Having a coffee, tea, or hot chocolate is heart warming. There are some alternatives to cooking and hydrating. Eat it uncooked like crunchy ramen. Lots of foods will still be safe after a few days between resupplies. I've read about hikers who hydrate all day long in clean peanut butter containers. The trick might be calorie density.

Lastly, depending on where you are hiking you might want to consider a second pair of shoes. The last time I was in the Southernmost part of the Big Cypress in the Florida Everglades the soles of both shoes fell off. So instead of relying on calorie deficit it's time to get to learning.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…