technology from back to front

PUTTING THE “GRRR” IN GRAPHS

In 2002 I was asked to add graphs to a financial website.

I started by considering off-the-shelf freeware Java packages, but a few hours of research suggested that none of them were quite customisable enough
(as may well still be the case in 2008, perhaps astoundingly). So I decided to write my own graph package – the third or fourth I’ve done, I think.

There was an immediate problem, because my boss thought it was all taking too long (this after a week or two) with not enough visible progress. The perception,
after I’d shown him a wiggly line generated on the first day by a freeware package (subsequently deemed inadequate) was “we’re going backwards”. It was clear that there was a potentially career-limiting loss of confidence here. Also, I was working off-site, and the company didn’t really have any way of monitoring me – adding to concerns that what I was doing might not be sensible.

The boss took to ringing me up more and more often to demand progress reports. Naturally, he would always do this just as I was in the middle of debugging the axis generator, or some other heads-down task, and so he’d get an unsatisfactory or distracted response… I was becoming a classic instance of a techie “going dark”, and crisis was imminent.

After one particularly painful meeting, I solved the problem by suggesting I send twice-daily email updates. This turned out to be a wonderful and rare example of coming up with a simple, effective management tool.

Typically, the emails would take 20 minutes to write and be 10 lines long, saying something like “I’ve done X, tried Y but it didn’t work because Z, am doing W next”. They didn’t generally require much feedback. The great thing was the discipline of having to report what I’d done every half-day. For all I know, the boss hardly ever read the reports, but this didn’t matter – by telling him what I was doing, I’d implicitly given him the opportunity to monitor it, in a non-intrusive way.

I’d describe what I was doing in the language of features, e.g. “shall I add a logarithmic scale option?”or “now I need to add a module to calculate and display dates
properly in different time ranges” and the response was generally something like “yes, great idea”. Confidence was restored.

I’m still proud of that graph package, a worthy successor to the DOS/Windows/OS2 ones I’d done previously. It took two months, and the main thing I
remember was that there were twelve off-the-peg graph sizes: Micro, Tiny, Miniature, Small, Pocket, Medium, Compact, Big, Large, Huge, Colossal and Gigantic.
(Pocket started off as “Undersized”, but I decided that name wouldn’t do.) Micro was so small that it only made sense as a footnote to other web pages. As for Gigantic, it lived up to its name, and was a response to certain awkward users of the website who kept complaining that the graphs weren’t big enough. Later on, I refactored it so that you could have dynamically updating real-time graphs with all the same sizes and features, viewable in an applet.

As for the “management technique”, I suppose it was a bit like Scrum. For me the moral was that you have to keep management updated, proactively if possible.
Also that it’s often reassuring to give people detail, even if they don’t want to drill down into it.

 

by
felix
on
19/03/08
  1. Phil Dawes
    on 19/03/08 at 4:48 pm

    I use a blog at work for exactly the same purpose. When I’m doing a project for somebody I don’t work directly with I blog my progress tagged with the project name.

    Another side effect of blogging progress is that others can keep track with what I’m doing and chip in with ideas and feedback. This is especially important when the project is skunkworks or against the political grain in some way, as it alerts people to things early and gives them a feeling of knowing whats ‘going on’.

  2. I agree that people like to be kept informed.

    I worked on a project where the manager was on site at the customer (we’re in NZ, he was in London). I quickly discovered that if I didn’t call him first thing in the morning (8AM NZ time), he would be impossible by lunch time, flame mail flowing as a steady stream from the UK to NZ. Even worse, the email wouldn’t be flowing to me, but to the entire team.

    For some reason, he never called me, nor did he ask for a daily status call.

    So, I did just that, called him every morning and the flames disappeared. On the days that I was sick, or unable to make the call (because of early appointments), the vitriol would start up again!

  3. +1 on using a blog (well, a dated text file open in a second buffer) to record progress through the day.

 
 


nine + = 10

2000-14 LShift Ltd, 1st Floor, Hoxton Point, 6 Rufus Street, London, N1 6PE, UK+44 (0)20 7729 7060   Contact us