Five for Friday (7/7/17)

img_0463.jpg

It’s another Friday, so here are five links (and associated background reading!) that I have found interesting in the last week.

Before we dig into that, a personal note. I’m shortly to leave my current employer, and whilst my next major gig is almsot confirmed, I am going to have a day or so free from the middle of August onwards to do interesting things (preferably paid). If you’ve a tempory, short term Dave-shaped hole to fill, please do get in touch.

  1. Interesting series of posts by Alan Mather on progress on digital government, focusing on the hits and misses at GDS. It will be worth keeping an eye out for future updates.

    Funnily, Richard Pope has also just finished publishing some retrospective thoughts on GDS. Is anybody getting the sense of an ending? It might be immanent, rather than imminent.

  2. Why we made our platform product open-source – some useful thoughts here from Comic Relief on open sourcing the code they have used to create Drupal based campaign websites. The post outlines some of the issues involved and is well worth a read. There has been a long running (GDS related) discussion about the difference between open source and coding in the open (is just chucking source code online for others to use ‘open source’?) and whilst working in the open in whatever way is generally a good thing, nonetheless code is only useful when you have coders who can do stuff with it, so isn’t always a panacea.
  3. Matt Jukes is assessing whether there is interest in an event “about blogging. newsletters etc and why they are good for organisations and individuals”. Sounds good to me. More background on why he wants to do it here.
  4. Tech beyond the market and the state? – really interesting ruminations on ‘civic tech’ from Cassie Robinson, with some nice definitions – including a focus on ‘community tech’: “Where people on their own choose to work together towards a common goal.” Looks like this will be an enquiry well worth following.
  5. Why large technology programmes fail and what to do instead – of all the things I’ve been responsble for in recent times as a manager of technology teams, getting to grips with the programme of work has been one of the trickiest and I don’t think I’m yet to actually get it licked. However, following some of this advice from Dave Rogers would be a damn good start.

As always, these have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.