When the GOV.UK Pay team noticed some test payments were failing, they set about working out what was happening and how to fix it. Here’s what they did.
How we consolidated the testing landscape for GOV.UK into a small number of practical rules that are bringing a new consistency to the way we test our code.
All websites run into errors. We’ve reduced our errors by over 90% and changed our culture around errors so they are identified, owned and resolved quickly.
Adding a ‘show password’ option to GOV.UK accounts looked like a straightforward task, but it was more interesting and complicated than we expected.
GDS are recruiting for someone to lead on creation of the next generation of GOV.UK’s technical architecture, and to head up the community of technologists who will build this future. Find out more information about the role and how to apply.
Frontend development is a growing role within government, and it’s a vital one, as the work is focused on the parts of government that citizens interact with most often. Iqbal Ahmed, frontend developer at GDS, outlines the main duties of the role.
Help the government build better services by joining the cross-government community to share knowledge and resources.
We’ve enabled HTTP/2 on GOV.UK to help improve the site’s performance. Here we look at what HTTP/2 is, how it improves performance, and the impact it has had on our users.
We’ve switched to using Docker ‘containers’ for our local development environment, which has made it simpler to use and less error-prone.
Whether you’re searching for micropigs or income tax, we've upgraded the Elasticsearch database that powers GOV.UK search to make it easier to find information.
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.