Skip to main content

review - altra superior 2

Last weekend I went for a hike on the Florida Trail. A small 4 miles section of the trail was a gravel road and my feet were in pain.

These merrell trail glove shoes were kinda nice. First off they are a size 10.5 and while they fit my foot length the height of my arch meant I did not have enough lace and tightening the laces cause hot-spots. While I wanted a barefoot experience in order to give my heel a break I quickly realized I really want a zero drop.


After some recommendations and internet searching and reading I found these: altra superior 2 (size 11) which I purchased on amazon for $64. I went back to buy a second pair but amazon wanted to charge me $82 for the second pair. In the interim the superior 3 is available and given the pricing and availability I'll wait for the 3 to drop in price.

I noticed a few things. The laces and the body of the shoe fit better. Duh, size 11 vs 10.5. The toe box was also big like the merrell but the insole was squishy almost gel but it was thicker and I expect will be better on that dirt road.


One big surprise are these inserts.  They are meant to be inserted between the shoe and the insole to give a little more rigidity to the sole in order to protect your feet.


they call it a stone guard.


I cannot wait for my next hike.

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…