Skip to main content

the perfect knife

I just finished watching a number of howto care for your Mora knife when I found this video representing the "perfect" knife. This is more of a complaint than howto blog because while this guy demos a sharp knife slicing paper to shreds.


I have several issues with using paper as the "test". First, it's simply not a real life use. Anyone using paper as a kindling is going to use their hands to shred or crumple it. Second, if you've ever used your really sharp knife to cut cardboard it get's dull right away.

I do not claim to understand the physics of a sharp edge but I know a couple of facts from firsthand experience.

  • the sharper a blade is less likely you are to cut yourself as a result of over powering the cut stroke.
  • The sharper ("super sharp") the edge the thinner it is and the more likely it is to crack or shred.
  • Once the edge cracks the duller the edge and the more work to get it to sharp again
So the reality... know your knife and understand what makes a "good" edge that lets you work longer without having to sharpen it.

Continued, I have a collection of knives. I've already given half of them away. What remains is a collection of Mora knives with varying blade lengths and widths. There is something to be said for making feathersicks when the wood is right but then there are so many other types of tinder.

Two years ago I tried to baton some firewood but failed terribly and ruined my knife.

Three weeks ago we went camping again and this year I was responsible for the bonfire. Besides the structure I also introduced fatwood. I do not believe I'll ever be able to construct the fire without liquid fuel. however, I was able to reduce the danger by starting the fire with a lighter instead of a flame thrower (butane torch). In one test fire making feather sticks from the fatwood helped ignite the fire right away.

During another hike we cut down a tree with a saw and sawed the tree into segments. I wish we had the ax as it would have let us split the logs in order to get to the center of the log. For the type of hiking and camping I do either the logs are provided or I gather deadwood or standing deadwood. I think the saw is the safest tool because there is little energy that is put into it to get the job done.


The Silky saw was a bushcrafters favorite but now it seems to be some model of a collapsing saw.



Axes are heavy and come in different sizes based on the task. I like the Mora axe to supplement the saw. The resin handle is light and the blade is sharp and takes an edge. The hammer side is kinda narrow so it won't be useful for pounding stakes. Axes are not particularly sharp in fact most are meant to act as a wedge to separate the log fibers lengthwise.


My SAK Farmer is an interesting knife in that it has an edge for making feathers and a saw for cross cutting but really it has a limited diameter. The folding nature of the knife does make it a little more precise and error prone.

So as I swing back to the meaning of this post; super-sharp is bad; sustained edge better; choosing the right took for the task.

UPDATE to sort of put a point on it...



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…