Skip to main content

Bushcraft approach to software development

I'm not going to draw exact analogies and in some cases not at all. I think they are pretty self evident.

keep a positive mental attitude - Larry Wall might have called this Hubris. It's the mental state needed to solve the problem to the point where there is satisfaction and the desire to move on.

reserve instead of preserve - there is something to be learned from the past, however, trying to preserve the past has proven historically costly and impossible. for example; the ten commandments, the dead sea scrolls, cave drawings, the library at Alexandria, git, svn, hg, cvs, vcs, sourcesafe, fossil and so on. Keep what you need in reserve in a way that is effortless.

cutting - in the bush having something to cut with is essential. The act of cutting can sometimes be a one-way trip. Consider deleting or renaming a file in production and what effect it might have. cutting reminds us to measure twice and cut once. You might be able to cut and tie that cordage back together, however, it's going to be shorter. This might also mean knowing what to cut from a project as it can effect time.

cover - keeps you try, the bugs out, allows you to collect water which is akin to having prepared for debugging, tracing, as an umbrella to all of the systems below. ELK comes to mind.

combustion - while combustion is going to generate heat to stay warm, dry out wet clothing, add mental comfort; too much heat and things burn and melt. It's important to know how to optimize your systems to take advantage of the heat without burning down too quickly. Efficiency. Creating tools that are not self service means you might be servicing them yourself and while it's fun to be a rockstar.... what have you done for me lately.

cordage - depending on the business you're in there must be an economy of scale. While Elon Musk built Tesla and Space-X very little technology was transferable from one business to another. I imagine he took what he learned from Tesla, improved it, and moved on to Space-X. He was the thread the bound the businesses together. It's great to be a polyglot. I pick the best language for the job and when once does not exist I create one. But if they do not embed or integrate they will be islands unto their own; like trying to join a vine with razor-wire.

container - keeping it all together, pure and safe. Docker and rocket are currently the best expression of this idea in it's literal form; and I also think about the monolithic code tree at Google versus project based code trees. There are some advantages to the monolithic tree, however, at google scale it might actually be too big. It's not until the combustion of the build process begins until the weaknesses can be observed.

** notice that the C's are actually multi functional.

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…