Week notes #16-21

Dafydd Vaughan on 23 September 2013

I’ve neglected my week notes for a little while so here is a condensed update covering week 16 to 21.

Part of the reason for the lack of notes is that I took a couple of weeks off towards the end of August. I tried to avoid using my computer during these weeks and completely cut myself off from anything work related. This inevitably led to an insane amount of work prior to my time off and a crazy period of catching up upon my reassimilation.

I have a really bad habit of pushing myself too much and I never realise how tired and unproductive I am until I actually stop. Time away from a project is essential and lets you come back and look at issues with a fresh perspective. I’ve got to make sure I don’t leave it so long to take time off in future.

A big focus over the past weeks has been the infrastructure for the View driving record project. This is the first service at DVLA to use some new technology (such as DropWizard, MongoDB and Nginx) and also new development techniques. We need infrastructure that lets us deploy quickly and regularly, we also need infrastructure that is flexible so we can scale the service as needed.

Designing and building out a new infrastructure isn’t a simple affair, even when you have models like GOV.UK to base it on. This is particularly true with DVLA as we have to integrate with some legacy systems such as the Driver’s mainframe.

I think it’s fair to say we’ve started this work a bit too late. While the complexity hasn’t surprised me, I think I underestimated the amount of time it would take us to get to a production-like environment for the service. In hindsight we should have started this work several months ago and built out the simplest production infrastructure we could then scaled and tweaked to our needs.

We regularly use the phase ‘deploy little, deploy often’ at GDS to explain our approach to pushing things to production. I’m starting to think that we should add ‘deploy early’ to it as well. I’ll certainly be taking this approach on the next DVLA project.

I’ve also spent a fair amount of time with the Iain Patterson, the new Director of Technology at the DVLA. We’ve been looking at the wider picture of how to design, build and run services like View driving record. This has involved things such as working environment, the types of kit that teams might need, infrastructure requirements, tools and policies/processes that might be needed.

In addition to all of this, I got to go to dConstruct in Brighton and spent time talking about APIs with the GOV.UK team.

Finally, this week I’m speaking at (R)evolution Conf in Shrewsbury on Friday about how we took GOV.UK from an idea to where it is now.

4 comments on “Week notes #16-21

  1. Hi Dafydd,

    I’m wondering if you can help – I’m looking to get in touch with Iain Patterson as we have developed a couple of products which link to DVLA services and wanted to pass them by him. Would you be in a position to share a contact address that I could reach him at.

    Also I’d like to say the above sounds very promising, the current services offered are incredible unfriendly and shockingly put together. Looking forward to seeing the end result.

    Best
    Chris Foulston

  2. Good day Dafydd. Perhaps you can assist me. We have developed and patented (under the PCT) an Electronic Vehicle License that incorporates several components – dual RFID tags – (i) Long range/ high speed reading and (ii) NFC – Near Field Communication for the patrol officer/meter maid. Windscreen based (front & rear), aGPS module with integrated SIM card for tracking and data transmission over a mobile network, a Photovoltaic panel for internal battery recharging and a socket for external power input.
    In view of the DVLS’s proposed migration from the old paper based car tax disc to an electronic system during the course of 2014, I would like to make contact with Iain Patterson but cannot find his personal email address anywhere. Can you assist?
    kind regards
    Darryl Cotty

Comments are closed.

Any views stated here are my own and not those of my employer unless otherwise stated.