Skip to main content

Winter hiking calories and food

Winter hiking is going to be a TECHNICAL pain in the ass with plenty of potential fun. In December I'm planning a 6 mile snow shoe hike and my biggest concern is that a 6 mile hike can become an all day event so it's important to have water, shelter, and food; more than anything else.

First Hike - 6 miles

Optional second hike - ?? miles
 In preparation I'm trying to figure out how many calories I need to bring with me. First and foremost there is a standing caloric need of approx 1200 calories with a winter adjustment of another 400 for a total of 1600. And snow shoeing can be from 420-1000 per hour depending on effort(400 calories at 2 mph on level terrain); plus the effects of elevation.

Food that is considered appropriate contain little to no water. Dehydrated food would be considered perfect but you need heat... therefore not so ideal if you do not have a stove; and I will not have a stove. Here are some food stuffs that I'm looking at.

I placed these two pouches in the freezer and they got very stiff after an hour. The honey almond butter was noticeably harder as there must be some moisture in the honey. The plain peanut butter softened right away. There is about 190 calories per 1oz pack.

I'll add some tabs to my water before I leave for the hike. These electrolytes have 8 calories per tab or about 54 calories. Since there is sodium in this product I'm hoping it lowers the freezing point of the water.

Jerky is going to be a good source of salt and protein calories. Each of these packets are 2oz and only 130 calories. The challenge here is that the honey has a higher moisture content and "fire" is not recommended when hiking in the snow and it may cause additional perspiration. And that'll kill a hiker.

I have additional calories on order and I'll test their freezing point when they arrive.

Each of these is about 100 calories, however, they contain caffeine and that is also undesirable.
My usual snacks are Trader Joes cookies, bulk chocolate broken into little pieces so it melts in my mouth, Ritz crackers which are loaded with butter and salt, small chunks of hard cheese or salami that I’ve cut up beforehand, gorp, brazil nuts, Justin nut butter packets which I squeeze into my mouth, packets of GU, Oreos, beef jerky, and small chunks of dried fruit. Another favorite of mine is Terra Blue chips which you can crush to make more room in your pack.
This quote came from an internet search with some sensible purchases for on the trail eating.

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…