From new development processes to cultural practices, Chris gives the lowdown on how developing at GDS is different from other organisations.
Find out about the Canadian government’s cross-government API Store, how the DVSA improved staff morale with mobile working, tips on delivering APIs as a product manager and more.
The GDS Reliability Engineering team had to find some inventive workarounds to get the Alertmanager open source software package working on a managed container service. Here’s a detailed look at how we did it.
The standards that underpin GOV.UK Verify have always been open but we started coding as a private project. Here’s a recap of our journey to coding in the open.
The Government Digital Service hosted an event for developers as part of the Global Day of Code Retreat. Find out what we did and why we set them an impossible challenge.
The cross-government event covered challenges the public sector needs to think about when considering the use of blockchain, voice assistants and artificial intelligence.
The cross-government open source meetup addressed common barriers to coding in the open, from hacking fears to licensing confusion.
At the Government Digital Service we've stopped using spreadsheets and software-as-a-service tools to manage our rotas and built our own app. We've open sourced the code, so you can use it too.
GitHub plays a major role in the software supply chain at GDS. All our source code is stored in GitHub - mainly in Alphagov - and we work hard to make sure our repositories are secure.
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.