Skip to main content

Review: CRKT Original KISS

It sucks.


It folds nicely and the action is ok. Rather than using the stud I found myself using the bevel of the blade to open the knife. The complaint is that when it's closed the DT is not strong enough and when open it's easy to close since the normal grip include the lock release. The only problem with the closed blade edge is that the point is pointy and not smooth against the frame. I was not able to correct that with my stones as I was never certain what angle to reduce.

The blade is ok and cutting  takes getting used to. The 100% edge causes the knife to move sideways in the target.



I think the designer was intending the user to wrap the blade with money so that the bills would act as a sort of sheath. Which is not a bad idea. But then you're not going to win any speed awards.

There is a lanyard hole and the clip appears to be removable. I do not think this would make a good neck carry as it is kinda heavy for that and dangerous too. Although a creative knot might render it harmless and useless at the same time.



Lastly this knife is about a 3 finger grip so it's a reasonable size. I think the KISS 2 or the slip KISS 2 might be a better knife for cutting something.  WARNING this is not something you want to take past the TSA. It could just land you in jail.

Popular posts from this blog

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…

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…