Skip to main content

you do not know what sharp is

I've been watching "how to sharpen your knife videos" and there is a lot in common.

  • choose an angle
  • stroke until there is a burr along the entire edge
  • if you cannot get the burr then switch sides
  • when you finally get the burr start counting, alternating and reducing the strokes
  • start with coarse only if the edge is damaged
  • use a ceramic rod between grit and strop
places where they differ
  • sharp when you can cut paper
  • sharp when you can shave your arm hair
  • how many strops strokes
  • how fast to strop
  • how much pressure against the stone
  • care for the stone
  • water, bio-oil, honing oil or none at all
One thing all these videos have is that they cut paper. Usually an 8.5" x 11" is torn to shreds like an Errol Flynn movie. One fellow even cut a paper towel. What's next a tissue?

Let's look at the following pictures. These images are taken from my test paper with 4 different knives. Mora Companion, Schrade42D, Mora Black, Ganzo 738. Two of these knives have never been used and two I sharpened using everything I know and own. (DC4, Nagura, WorkSmart 4-1). Each of these cuts is thinner than the thickness of a dime. And some feathers have been thinner than a human hair (not pictured)





I don't know if my sharpness tests are a true test but I know for certain that it took a while to get these right and yet I've come to the conclusion that sharpness is only part of the equation. There are two attack angles for the blade to the paper. There is the pressure into the paper and the speed of the stroke. While I was tinkering with my Schrade bowie knife I was able to create a few of these paper feathers but VERY inconsistently.

Only one presenter said, of sharpening his ax with a Lansky puck stone, it just needs an edge that it can hold. Since he did not paper test the ax I assume he meant that the paper test was superfluous.

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…