-
Exploring a new way to make eligibility rules easier to implement
October 16, 2018
onWhen federal agencies issue a policy change, say income eligibility guidelines, that policy gets communicated down to the states as text on the Federal Register or via PDF. This translation of federal policy into many state systems creates opportunities for implementation errors.
-
Implementing rules without a rules engine
October 9, 2018
onIf you’re building a rules-based system, don’t assume that you need a separate business rules engine product. Rules can be implemented more easily and with less overhead by cross-functional teams working to describe the rules and policy directly in code using a general purpose programming language like Python, Ruby, etc.
-
Am I doing this right?: Antipatterns in agile contracting
September 27, 2018
onAs agencies try to adopt agile development practices and modular contracting methods, there are several anti-patterns that we have noticed through the course of our work. We address how these can hinder success and alternatives to consider.
-
Shared infrastructure as code
August 15, 2018
onAt 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.
-
ETL: Extract, Transform, Learn
August 9, 2018
onProviding 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.
18F Blog
Delivering civic technology
Page 24 of 102