Monthly Archives: November, 2012

Feed on this…

For some years, I had a handy sign-up form on the right-hand side of Status-Q allowing you to receive new entries by email, thanks to the good folk at FeedMyInbox. Sadly, they’re going to be closing down at the end of the year. As an alternative, you can use IFTTT to create RSS-to-email recipes.

However, since the most-used RSS reader out there, by far, is Google Reader, and the various apps that can sync with it (my current iPad favourite being Reeder), I’ve replaced the FeedMyInbox link with an ‘Add to Google’ button, so it’s dead easy to include Status-Q in your Google feeds, should you so desire.

Lots More Pots

Following on from the article mentioned yesterday, the World Service broadcast about the Trojan Room Coffee pot went out today.

Links to the programme, and a downloadable version here, if wanted.

Change management…

There’s an amazing thing I’ve just discovered after installing an SSD in my laptop: Microsoft Office products now start up at a reasonable speed!

I’ve only just realised that, because I open them so rarely. (It’s one of the joys of working for myself that I can largely pick the tools I use.) In fact, I realise, I probably download updates for Office components more frequently than I actually use them.

That’s an interesting phenomenon; there ought to be a word for it. I’m probably unusual in having Microsoft Word work that way, but there are many of my lesser-used iOS apps that will be updated several times between successive actual executions of their code.

This is a real cultural shift from a world where big corporations would debate for months before rolling out an update to a program. On the web, we’ve grown used to the idea that a piece of software might not look quite the same the next time you log into it. But it’s now true of many apps in my pocket: something will have changed in an app before I run it again. I could quite easily pull my phone out one day and discover that last night’s update had broken something and I could no longer access the boarding pass I need for that plane…

I guess it’s a tribute to progress in software development, or perhaps to the Apple software-approval process (a real pain for developers but in many ways a boon to customers) that this so rarely happens.

Lots of Pots

Regular readers will know this story well by now, but there’s a piece on the BBC Technology site about the Trojan Room Coffee Pot, by Rebecca Kesby.

An audio interview with me, Paul Jardetzky and Martyn Johnson goes out on the BBC World Service tomorrow. Haven’t heard it yet…

Virginia Water

Autumn in Windsor Great Park yesterday afternoon.

ANDIY – the Art of Not Doing It Yourself

The best way to learn about car maintenance, I’ve always felt, is the way I did it in my youth: have cars cheap enough and elderly enough to need regular repairs… and not enough money to pay anyone else to fix them for you. My first three cars combined cost me less than my current phone, and, while it’s been a long time since I last stripped down a carburettor or replaced a leaf spring, it’s pleasing to know that, should the need arise again, I wouldn’t be completely unprepared. (Actually, now I come to think of it, the likelihood of either of those particular needs arising is becoming rather remote, but you get the idea.) These days, I tend to pay someone else to fix the car, but at least I can sometimes sound sufficiently knowledgable to dissuade them from ripping me off!

Often, that’s the pattern of growing up. You prove to yourself in your youth that yes, you can hang wallpaper or lay a patio, and you go to bed with a sense of achievement and the satisfaction of saving lots of money. As you get older, sometimes, the satisfaction comes from being able to afford a professional to do it, not, of course, because you are helpless or incompetent — you’ve proved twenty years ago that you aren’t — but just because you have more important things on your plate right now. And, actually, the professional did rather a good job, you have to admit…

When the job might be deemed to fall within your own profession, however, it’s more of a struggle. I have, for much of what might laughingly be called my career, earned my daily bread by writing software, or setting up companies in which other people can write software, and I greatly enjoy doing so.

So, while I have no desire even to attempt the creation of, say, another Photoshop or Excel — I have more important things on my plate, you understand — I have sometimes been reluctant to pay for simpler utilities because I feel that I really ought create the same functionality myself, just as soon as I get around to it.

Well, a couple of recent purchases for my Mac have convinced me that this is often a foolish attitude. If someone has gone to the trouble of creating a nicely polished utility that does just what you need, it may be worth a few bob to tide you over until you get around to building your own string-and-sealing-wax version. Who knows, you might find the (other) professionals did rather a good job…


The first of these is Hazel, a utility that monitors folders in the background and performs actions on the files in them, based on certain rules. It’s the sort of thing any decent programmer might dismiss as being for those poor sods who can’t throw together a cron job, folder action and a bit of Perl when they need it. And actually, the idea of monitoring a filesystem as a way of initiating tasks is not, perhaps, a natural one for computer scientists, who would generally think of more efficient ways of kicking off a process. But it can be incredibly handy, starting with simple things like making sure your desktop or your downloads folder doesn’t become too cluttered: Hazel can file stuff away in neat subfolders (or the Trash) if it’s been hanging around there too long.

Then you listen to podcasts like this one and this one, and you realise that when you scan a document into whichever folder your software cares to dump it, Hazel rules can pick it up, send it to your OCR program if needed, rename it to include today’s date, and then, if the OCRed content includes the words ‘HSBC’ and ‘statement’, file it away in the appropriate folder where you keep your financial records. It’s like putting a bit of paper in your out-tray and having a secretary pick it up, classify it appropriately and file it away in your filing cabinet for you. Nice.

Hazel becomes especially powerful when combined with Dropbox, where things you drop in a folder on your laptop while away can be handled by Hazel on your desktop back at home. You need to get into the mindset, so go and find out what other people are doing with it, and you’ll start to realise what it can do for you.


Arq is an off-site backup program. There are plenty of those around – Carbonite, Crashplan, Backblaze, etc. But this has a couple of key differences. Firstly, it’s not a service, it’s an app purchase. You buy it once, and you use your own Amazon S3 account for the storage. The format in which it’s stored is fully documented. You can specify your backup budget — “I want my home directory on this machine not to cost me more than $8/month” — and Arq adjusts the amount of history it stores to keep within that figure. And if you have several machines, or if you provide IT support for your family and they’re all happy to backup to the same Amazon S3 account, you can check up from one machine on the backup status of the others. Finally, it’s just been updated to allow use of the new Amazon ‘Glacier’ storage. If you’re willing to put your data here (where it may take a few hours to get it back), it’s an incredibly cheap backup. If you have on-site backup as well and this is just for real emergencies, Glacier may be a good option. Either way, Arq handles it nicely.

Day One

For the last six years or so, I’ve been keeping a ‘journal’. (For younger readers, a journal, or diary, is like a Facebook or Twitter account but without any followers. Huh?) Mine’s not really a diary, so much as a cross between a lab notebook and a set of Post-It notes stuck on the screen: odd notes jotted down, URLs, booking references, phone numbers, snippets of code… but it’s very valuable and I search it regularly to jog my memory. I used to do this in a big folder full of text files, named according to the day concerned, and a set of keyboard macros and editor configurations to make it quick, easy and relatively nice looking. Then I discovered Day One, a journalling app for the Mac, iPhone and iPad (it keeps them all in sync), which makes it even quicker, easier and much nicer looking than my system. Its format is also reasonably straightforward, so I was able to import my six years of past notes, and can be pretty confident of getting everything out again if needed. It has a feature which I thought would be irritating but am surprised to find I rather like: it can pop up a little box in which you type your current activities or thoughts and then just hit Cmd-Enter to save. You can set it to do this a given number of times per day – three, in my case – and it’s a very low-overhead way to keep a track of what you were doing and when.

All of the above come highly recommended – and, for the record, I have no connection with any of them other than being a happy customer. Feel free to comment with thoughts on any of these, or indeed tales of any other ways in which you are becoming a skilled ANDIY practitioner…

GRUB, Ubuntu, and failed boots

Another geeky technical post. Ignore if it’s not your thing….

I wrote recently about the GRUB bootloader and how it can sometimes cause a remote or headless server not to come back online after, e.g. a kernel update.

This can happen in other situations: The configuration used on recent versions of Ubuntu is such that, if the system thinks that the last boot attempt failed, it stops it automatically booting into the same configuration again by cancelling the countdown timer, setting the number of seconds to -1, causing it to wait indefinitely at the boot menu until you decide on the best action to take. This is a sensible default, because a machine that goes into an infinite loop of reboots is doing nobody any good and puts a fair bit of strain on its own hardware.

Unfortunately, though, other things can trigger this behaviour. If you have a power fluctuation, for example, such that the machine restarts, gets part-way and then power-cycles again, you may find yourself with a machine that doesn’t come back online of its own accord.

On the most recent Ubuntu versions (12.04 with updates, and later) you can add a setting to /etc/default/grub:


for a 30 second timeout after it has recorded a failure condition. You can use 0 if you don’t want it to pause and show the boot menu at all, but remember that it could then go into fairly fast repeated reboots if something really does go wrong.

On earlier versions, you’ll need to edit /etc/grub.d/00_header and find the line near the bottom, in the maketimeout()_ function, which sets

set timeout=-1

and change that to your preferred value.

In either case you’ll then need to run:


to make your changes take effect.

© Copyright Quentin Stafford-Fraser