Skip to main content

Getting things done, read, or a reply

I'm not a productivity guru but in a recent conversation with a client of mine we started to hash out why his vendor was not responding to more than a few of the questions posited. In some sample emails there would be several one sentence questions and in others there might be multi paragraph descriptions before any number of questions. In the end we always seem to defer to a conference call. (I really wanted to get things going in an email because there was logical sense to the discussion.)

Then there is the resume. Recent studies (not sited) suggest that a one-pager is the best way to increase the likelihood that your resume will be read. I have both a one-pager and a multi-pager. With my history it seemed to me that a narrative approach rather than the usual boring: assignments, roles, responsibilities, languages, frameworks, etc... would make sense. And besides it no longer fits.

When I worked for NaBanco, later First Data, (circa 1994) we had a "one-pager" to describe all systems changes. Presumably if it tool more than a page to describe then it was too complicated and it needed to be split into separate change requests. It had not occurred to me before this moment but this is clearly an Agile process and it was definitely pre-agile manifesto(copyright 2001).

So by extension; if you were writing a how-to or a best coding practices document for your company you might want to take the same advice. Of course this does not mean 6pt font but it does mean a consistent and well formatted document that is compelling to read. The good news is that this is a good task for a document writer and not a programmer.


  1. HI Richard,

    As an IT Manager, I was responsible for hiring in my previous (small) company. When a CV consisting of multiple pages landed on my desk, I immediately threw it. No time to read it.

    Now as for vendors not replying, sometimes there are things that are stuck on their end and that they don't want you to know about, and that's why they don't reply (it's no because the email is long or a has a lot of questions). You might notice that the will skip a couple of questions and then answer one or two.

  2. A very 'C' level executive once told me that on any given day the "new hire" process is never going to be in the "top ten" list of priority things to do. Something is always going to come up. This combined with the speed and attention of the internet-age ... resumes should be one page with plenty of whitespace. The challenge is to keep their attention long enough to make it to the not-no pile.

    Would you hire me from my resume (

    Email is tough. While it covers a conversation between people or groups it's not good for multipoint discussions. Even most bug tracking systems and knowledge bases fail when it comes to questions that fork. To the email point, unless the email is formatted properly the respondent is probably going to skim the email rather than read for detail.

    Regardless, when people cherrypick the questions they are going to answer they are not helping. In fact it's as if they did not answer the question in the first place. Specially when the questions fork.

  3. Hi Richard,

    The link that you gave me seems like a biography, and not like a resume.

  4. Yes, that's true. I intended it to be a one-page narrative instead of a traditional "company, title, dates, description". My reasoning is that a) I cannot get my relevant experience in one page using the traditional form without eliminating the borders and microscopic fonts; and b) I wanted a way to convey the sum benefit of my experience. The other point that I wanted to make or imply is that I do not want to be compared with freshman programmers. While there is a certain financial incentive for hiring freshman you need a different kind of support system to keep them productive and keep the team well oiled. (Keep in mind that it was veteran programmers who wrote the Agile Manifesto not freshman).


Post a Comment

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…