Skip to main content

Hiking VLOGS are definitely bullshit

I started watching "how to make fire" videos when I failed to light up the fire pit at an indian princess gathering. I mastered that pretty quickly, however, youtube's recommendation engine started me down the path of "survival" from which I see that the 5 or 10 Cs and Rule of 3s are still pretty valuable. But there was a point when these presenters seemed off the rails.

And so I started watching hiking VLOGS. Many were AT thru hikers. That turned into PCT, ADT and CDT. And I am here to say that these people and their "hike your own hike" are likely full of crap.

To start; in a previous post I said that UL and SUL hiking was BS and I showed that with sensible choices it was impossible to get to a base weight that was safe. Sure, at least a 3rd of my pack weight was from things that I never used like my first aid kit and water filter. But then those ounce counters also stop counting things that they carry rather than pack. Like not counting the weight of the trekking poles even though they only use them half the time.

While that has to do with gear it's not my hiking rant. Here goes:

We got to camp at 7:30p and sunset was at 8:00p. The first mission was to put up our shelters. That took basically no time.

Carpenter Camp - Big Cypress - Florida May 2018
The campsite was moist but dry (if that makes sense). Clear skies and an evening temp of 71F. We were able to make a fire with some standing deadwood. We had nearly 5 hours of fire. The first thing I noticed was that gathering wood is a dirty job. If you have limited camp soap and water or hand sanitizer this might not be a good idea.

So #1; fires are recreational and can impact sleep and supplies. I would guess that if you're at a shelter that the person making the fire is not a thru hiker. But even so; spending so much time on the fire distracted up from other things.

#2; we did not make dinner until after it was pitch black. That made hanging the bear bag near impossible. While dinner was recreational the longer it took the more likely we were not going to be able to get everything hung as it should. And let's not forget that cooking a meal requires cleanup. That's extra water and food bits. And let's not forget that input equals output meaning if you eat dinner you might have to poop too.

#3; Bio breaks seem to be the most under represented topic. The AT manual talks about 80 yards or feet from the trail. That's a long way and possibly easy to get lost. One hiker suggested leaving you pack on the trail as a signal. That might not be safe [a] stolen gear [b] getting lost and so on.

#4; just exactly how does resupply work? Assuming that you go to the grocery store how much of what you buy would be considered bulk and what is the premium cost for buying travel size of hand sanitizer and insect repellent?

So in conclusion:

  • gear costs more than, weighs more, and is more voluminous than you think
  • you're never carrying enough water and the 1L per 4 miles is way off base
  • you need to know your schedule like the back of your hand and that means early to bed and early to rise and it also means you must have a rhythm 





Comments

Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

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

TL;DR;

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…