When leaving my last job I decided to do an exercise which compares what other people think my strengths are with what I think my strengths are. This is a write-up.
I think GDPR is great. I am really pleased that companies are now being more thoughtful about how they handle my data. For SPA, a conference that has been running for over 20 years, this coincided with a project I had already started to clean up the user data, and here’s what I did.
A few weeks ago I talked about how coding in the open can help you release faster at PipelineConf. This was my last talk as Open Source Lead at the Government Digital Service. Here is the video, slides, links, and a bonus sketchnote!
The SPA conference website deploys to production automatically on merge to master. It is on shared hosting, and setting this up with Travis was a bit tricky, so I’m blogging how I did it in case it’s useful for others.
One of my main aims as Open Source Lead at the Government Digital Service was to make sure that there were good resources in place to help people code in the open. Many of these didn’t exist when I started the role so I created them. I’ve collected useful resources here.
Every digital service designed within government has to meet the Digital Service Standard. One of the requirements of the standard is that new source code should be made open and published under an open source licence.
I have been the Open Source Lead at GDS for a year now. Here are some of the things I’ve achieved and learned.
In August I gave a talk about coding in the open in government at Turing Fest. The video has just been published and you can watch it on their site (you can skip the email request).
I usually publicise new posts on Twitter, though I also have an Atom feed. However, Twitter relies on people seeing it at the right time, so I’ve set up a mailing list for new blog posts (and possibly very occasional annoucements).