Skip to main content

Getting ahead of the pack in an Agile world?

I just bought 6 books from PragProg adding to my expanding library of eBooks on the subject and taking some cues from real life and experience I want to know "what is it going to take for me to receive the highest salary increase" when salary adjustments are handed out?
However every industry has it's laborers and architects --Richard Bucker

Historically salary adjustments had many different names. (i) cost of living increase (ii) merit increases (iii) bonus and so on. And in pre-agile times managers would rank employees. First everyone might receive a basic or flat rate adjustment ... for surviving the previous year or as a part of profit sharing. And then, using the ranking, the manager would increase the employees from a shared pool at the managers discretion based on any subjective or objective criteria.

However, in an Agile world where managers are supposed to be looking for marathon like sustainable development, what criteria should a manager use to rank or reward employees? For some employees overachieving comes naturally, for others it takes a lot of time or effort. The former will demonstrate sustainable performance and maybe some personal growth. The later will eventually burn out. Since the goal is sustainability it is going to be incumbent on the manager to NOT burn out the employees, therefore, either the bar is set lower to accommodate the average employees or only the best will do. (However every industry has it's laborers and architects)

The fantasy world of Star Trek is based on a meritocracy. If you have the aptitude to be a starship captain or a gardener you'll be assigned to that task. As for actual compensation I cannot remember it ever being discussed except in the rarest cases. Agile would have you believe that a meritocracy exists in this world too. If it is them maybe we are actually in transition... and while I cannot tell whether it's a good thing or not... I want nice things and I want to make sure that my employees can have nice things too. But for this to work I need to reward them somehow.


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…