Podcast: Technologists at GDS
Himal Mandalia and Louise Ryan join Louise Harris on this month’s podcast to chat about the breadth and depth of what technologists do at GDS.
You can find more information about technology on the dedicated Technology in government blog.
Himal Mandalia and Louise Ryan join Louise Harris on this month’s podcast to chat about the breadth and depth of what technologists do at GDS.
We finished the experimental first phase of the GovTech Catalyst, which helped us learn where emerging technologies can add value. We learnt this in collaboration with smaller technology companies. In our next phase, we will see prototypes develop into testable products.
The Notify team has adjusted its method of sending out text messages to maintain Notify's reliability. In this post we explain how it was done.
GDS has formed a Sustainability Network. One of our first tasks was to find out how much CO2 our digital services produce.
The Innovation team at GDS is working hard to bring the objectives we outlined in the Government Technology Innovation Strategy to life, and looking for new opportunities across government. Sue Bateman shares the team's next steps.
Be part of the GDS Academy's new programme and join a team of specialists helping to solve government’s most difficult problems.
GDS’s open standards lead Terence Eden joins us on our latest podcast. He talks about his mission to make government more open and the risks and rewards of emerging technology.
GDS has used pair programming since its inception. It plays an important role in building our services. In this post, Mervi Tyczynska explains how to pair programme effectively in 6 steps.
We've just updated the Technology Code of Practice, which sets the standard for how government should design, build and buy technology. The updates we’ve just made allow continuous iteration, and we expect that the Code of Practice will constantly evolve, and keep up when technology changes.
For any service to be put in front of the public, it has to meet the Digital Service Standard, a set of 18 criteria. One of them is that all new source code is made open and published under an open source licence. In this post, Anna Shipman explains why coding in the open makes things better.