Skip to main content

where was my knife made

One of the things I hate about Amazon is that you can never tell where a thing comes from. Was it manufactured or sold in the US or some other country? In particular I purchased some cordage which, after the fact, took nearly a month to arrive because it was coming from the APAC.

Now recently I started looking for a new EDC knife and as I was looking at the Gerber site I determined that not all of their knives are made in the US. So I started looking for a folding knife that was US made and the first stop was Gerber. It seems that only two modes are made in the US and they cost $150 and $350 respectively. I agree that part of the cost is due to the high-end nature of the individual knives and the other part is labor. I supposed there is nothing wrong with that too, The sad reality is that the US knives are beyond my price range and a competitive knife will probably be crappy as they have to cut corners somewhere.

SOGs new knives for 2016 are in the same vein. They have a few more models than Gerber but they are mostly $100+. I watched a 2016 new model presentation and I was embarrassed for them. I supposed they could be the Rolls Royce of folding knives, however, if it cannot tie my shoes or butter my toast they cannot justify the price. I might feel differently if I had one in my BOB but not right now.

Kershaw was a complete surprise. While they are a subsidiary of a Japanese company they make their knives in the US. In fact their website features a filter that includes "made in the USA".

That's what I call confidence. I could not tell the difference before and after the filter. But when I started applying filters to make the search comparable the prices were at least double the cost of my Ganzo.

Columbia River Knife and Tool seems to be an exciting company. They make a number of interesting products, however, while there are some product descriptions that say Made in the USA there are other that say nothing.

** one feature that seems to be adding considerable cost is the assisted open. Are people really that lazy?

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…