Skip to main content

Review: Benchmade HK Knives Ally Knife

There are a couple of things to like about this knife but not enough as an EDC.


  • lightweight
  • low profile
  • smooth one handed open
  • with caution a one handed close
  • reasonable blade length for an EDC
  • glass break
  • serrated edge
  • chamfered blade spine and lock release is uncomfortable
  • no edge for fero rod
  • don't leave it in a hot car
  • grip
Let me detail the CONs because if you already like the knife there is no reason to look passed that.

I take issue with the serrated edge because it's just one more thing that needs to be cared for. If you've ever sharpened a knife to near razor sharpness now you have two blades to sharpen. Yes, it's just more work and plenty to do with your down time in your tent. **I did a featherstick test with my HK and it worked nicely. It grabbed the wood and created multiple feathers with each stroke. I then created grooves in the wood that made the finer feathers. Re-positioning the blade from stroke to stroke was a little more challenging and required more practice. I'm just saying that a serrated edged was not any more or less functional.

The chamfer on the blade is deep making it uncomfortable with a tight grip. And the chamfer on the lock-release both in the grip and when releasing the blade lock.

Simply put the spine of the blade is powder coated and lacks a 90 degree edge so the only way to strike a fero rod is with the blade edge. I guess that's OK but it's a sensibility thing for me.

It's a metal skeleton frame so it's going to get hot in your car. I suppose that's kinda contra-indicated when you consider that there is glass break... let's just hope you don't drop it when you need it most.

And lastly the grip... it's not a full sized knife and so the grip is going to be awkward. There are clearly two normal grips. [a] forefinger in a channel on the blade and [2] just behind that position and [3] as a chopper but you better have a lanyard for safety.

It's a well made knife that is better as a letter opener than an EDC.

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…