Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 142
  1. Slack

    I’ve written briefly about Slack before (at the end of my post on High Output Management), but this year I decided to re-read it.

  2. This year, I finally read The Effective Executive.

  3. Triggers

    Triggers is a very interesting book.

  4. Earlier this year, I read What Got You Here Won’t Get You There.

  5. No next Next

    Last week, I wrote about how we worked out our tech strategy for FT.com.

  6. When you are launching a new product to replace an existing one, it’s easy to rally behind the mission and make the right technical decisions that will get you over the line.

  7. After you launch a new product and no longer have the launch to work towards, it’s very easy for things to drift off track.

  8. Last year, I met the excellent Russell Davies to ask his advice on how to create a strategy.

  9. I’m the Technical Director of Customer Products at the Financial Times.

  10. A while ago, the excellent Russell Davies gave me a copy of Good Strategy, Bad Strategy.

  11. This is the first role I’ve had managing a large budget and I recently had some excellent training from my finance director colleague Isabelle Campbell.

  12. Building relationships with vendors is an important part of my role as Tech Director and when I joined the Financial Times, the excellent Rob Shilston gave me his five top top tips on how to make the most of those meetings.

  13. Last April, I joined the Financial Times as Technical Director for FT.com.

  14. When I joined the Government Digital Service in April 2012, GOV.UK was just going into public beta.

  15. Interviews are not a great way to find out how good someone will actually be at the job.

  16. Earlier this year I read High Output Management.

  17. I had long been thinking I must move the SPA site to HTTPS.

  18. As part of my ongoing mission to update the SPA conference website, I had long wanted to replace the CMS.

  19. 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.

  20. I think GDPR is great.

  21. A few weeks ago I talked about how coding in the open can help you release faster at PipelineConf.

  22. The SPA conference website deploys to production automatically on merge to master.

  23. 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.

  24. Every digital service designed within government has to meet the Digital Service Standard.

  25. I have been the Open Source Lead at GDS for a year now.

  26. In August I gave a talk about coding in the open in government at Turing Fest.

  27. I usually publicise new posts on Twitter, though I also have an Atom feed.

  28. There’s a task I have to do every now and again for which awk is the best tool, but it’s infrequent enough that I always have to remind myself how.

  29. I run the website for SPA conference.

  30. I run the website for SPA conference.

  31. There are two big concerns government organisations have around making source code open.

  32. For any service to be put in front of the public, it has to meet the Digital Service Standard, a set of 18 criteria.

  33. Earlier this year I had the opportunity to work with my excellent colleagues Rosa Fox and Lucy Carey on a series of workshops to help get more underrepresented people in tech into public speaking.

  34. We are hosting the second cross-government meetup on Open Source in London on Tuesday 26th September.

  35. I help run SPA, a workshop-based conference on all aspects of advancements in software development – technology, processes, people and practice – and we are looking for people to join the organising committee for the 2018 conference.

  36. As I become more senior I have more of a need to write business cases.

  37. We are organising a series of cross-government Open Source meetups to exchange ideas, talk about code we can reuse or collaborate on and build a community around Open Source.

  38. I was recently appointed Open Source Lead at the Government Digital Service (GDS) with the aim of making more government code open, improving the reusability of the open code we already have, and helping government as a whole be a better member of the Open

  39. I’m pleased to announce that I’m now Open Source Lead at GDS.

  40. How to blog

    Someone recently asked my advice on blogging, particularly how I decide what to write about and whether I set aside specific time.

  41. 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.

  42. When I started line managing people at work, three years ago, I got some great advice from the excellent Andrew Seward.

  43. At Scale Summit last week I led a session on code-sharing in large organisations.

  44. We previously wrote about looking into offering a platform to host digital services.

  45. Video from my FFconf talk Operations: a developer’s guide.

  46. Slides from my talk Operations: a developer’s guide, at FFConf 2015.

  47. I gave a keynote at Velocity EU about the work I’ve been doing on a PaaS for government.

  48. 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.

  49. Right now, hosting services is one of the most time-consuming barriers for new digital services, and usually involves duplicating work done elsewhere.

  50. Until recently, career development for technologists at GDS was relatively unstructured, and dependent on what opportunities came up.