I’ve had this blog for five years, but I’ve only recently started using my phone to browse the internet, at which point I realised it displayed terribly on a small screen. It’s a wonder anyone ever read my posts.
When I started line managing people at work, three years ago, I got some great advice from the excellent Andrew Seward. He structured one-to-ones around the following list of questions:
At Scale Summit last week I led a session on code-sharing in large organisations. I was particularly interested in how other organisations raise the visibility of shareable code. This was one of the main themes that came out of the recent code-sharing unconference at GDS.
We previously wrote about looking into offering a platform to host digital services. This post is about the technology we chose for the beta and how we made that decision.
Video from my FFconf talk Operations: a developer’s guide.
Slides from my talk Operations: a developer’s guide, at FFConf 2015.
I gave a keynote at Velocity EU about the work I’ve been doing on a PaaS for government.
I’ve been working on a prototype of what a Platform as a Service (PaaS) for government might look like, as we wrote about in a previous post. One of the first things we did was look at the open source PaaS options that were available. This post is about how we did that and what we learned.
Right now, hosting services is one of the most time-consuming barriers for new digital services, and usually involves duplicating work done elsewhere. On the Government Platform as a Service team we’re working on solving that.
Until recently, career development for technologists at GDS was relatively unstructured, and dependent on what opportunities came up. Over the last few months I’ve been leading on developing a more structured career path for developers and web operations engineers. This blog post describes what that involved.