Skip to main content

A heads up to recruiters and agencies

I think I've beaten this to death. [a] do not send your junior screen scraping and email spamming freshman recruiters or agents to contact journeyman programmers. You are elongating the process and wasting everyone's time. [b] get your credentials right. And by that I mean (i) if you're a person with a decidedly foreign name you might want to reconsider calling yourself "Bob" and stick with your given names and if you want to be called Bob then learn the syntax for nicknames. (ii) you probably do not want to reuse a single premium account without changing the email address, email alias and email body signature. (is your name Steve, Joan or Andar). If you cannot afford or use your tools I don't think you're going to be working the side of the hiring formula that is best for me.

So have a nice day and may we all find our retirement opportunity.

UPDATE: WTF! I just realized that [b] was using StackOverflow. StackOverflow is cheap as dirt with a favorable refund policy. Recycling the contact name 3 times is a disgrace.

UPDATE: I did not link to my post because linking is supposed to up your Google ranking but that's not why I write. So as a reminder my first complain is when the recruiter does not understand [A] the difference between an entry level position, apprentice, experienced and journeyman. And it's [B] particularly annoying when the caller does not have the position information or enough information to make a decision.

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…