Skip to main content

management by dungeon master

I've read a number of books on management; herding cats and management by baseball come to mind but neither speak to my personal experience in management at different levels.

When I was younger I played traditional pen and paper Dungeons and Dragons. I played for many years and many variations of the game. Many times I was a player and others I was the dungeon-master. All of that fun came to an end when I was about 35 (and still playing geek games).

I read an article on the subject of "being a better DM". The conclusion of the article was basically this. Good Dungeon Masters cheat to keep the players interested, engaged and to direct the players in the direction of the story line.  When you think most dungeons are random they are to an extent. Either you keep battling random monsters until you find your way or you die.

And so looking back at herding cats and management by baseball and debugging the development process... while sometimes you fire the rockstar for the sake of the team... there are managers who simply refuse to promote or reward the right people essentially cheating. 

The difference between cheating in the game is that it JUST a game. Where cheating in the workplace is contrary to the social and business contract between employee, company and management. As a manager you have the responsibility to be transparent; set clear career development plans and goals; and provide timely, fare and accurate reviews. And let's not forget plenty of carrots when appropriate. As a manager if you cannot promote or champion an employee you have a responsibility to the employee and the company to "rinse and repeat" or to separate.

Management by dungeon master is not a desirable trait and in my personal experience it's only happened twice in the same company.

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…