18F Blog

At many government agencies, a central IT team manages DNS directly. Other teams must request changes using help desk tickets, which can have inconsistent turnaround times, and are susceptible to human error. Having DNS records as code and doing changes through pull requests brought turnaround time down from multiple days to under ten minutes.

Providing government data to the public almost always requires building a data processing pipeline between its place of origin and the systems that will serve it. Data must be copied, transferred between digital storage formats, reshaped to meet the needs of reporting systems, groomed for readability, and cleansed for accuracy.

As part of our work building login.gov, a single sign on service for government, we’ve been looking at ways to effectively verify people’s identity online. Not only did we need to find a technology solution to meet this need, we need to find a solution in a stack of brand new possibilities.

Ask 18F is an advice column that answers questions sent in by federal employees. In this edition, we’ll talk about how to recruit tech talent in government

In 2015, 18F had an idea for a better way for federal agencies to hire private vendors to build products and services using agile development techniques. We wanted to see what would happen if we used an existing government process (called a blanket purchase agreement) and tailored it to the needs of agencies looking to update their digital services.