Skip to main content
This is not an official government website. Views expressed here represent the personal opinions of current and former federal employees.

Blog posts by [Vivacious Herring]*


  • 18F's engineering craft practices at 10

    on

    18F engineering has grown and matured as an organization over time. We recently celebrated our 10th anniversary delivering better government services to the public. To support continual investment in our practices, we are renewing our commitment to regularly publishing what we learn, and creating a new engineering leadership role at 18F.

  • Catching up with the TANF Data Portal project

    on

    Around 800,000 low-income American families receive cash assistance through Temporary Assistance for Needy Families (TANF) each month. 18F and the Administration for Children & Families’ Office of Family Assistance partnered on building a new data portal for TANF. We caught up with Office of Family Assistance leaders to see how their agency is continuing with the work.

  • 18F Checks In With the DAWSON Project at the U.S. Tax Court

    on

    The United States Tax Court is an independent federal court that settles disputes between taxpayers and the Internal Revenue Service. Since the 1980s, the Court has used a modified commercial software product to manage its operations. In December 2020, the Court introduced DAWSON, a modern open-source case management system developed with assistance from an industry partner and 18F. DAWSON streamlined Court operations and changed the way the public interacts with the Court.

  • 18F Checks In With [Jovial Chipmunk]* and the eAPD Project

    on

    At 18F, we like to keep in touch with our project partners. 18F partnered with the Centers for Medicare and Medicaid Services (CMS) from December 2017 to June 2020 on the development of a product called eAPD. We caught up with [Jovial Chipmunk]* of CMS, the product owner of eAPD.

  • Navigating ATOs

    on

    ATO processes work differently at different federal agencies. As a technology and design consultancy inside the United States government, 18F has worked on ATOs at many of them. We are still learning and experimenting, but there are definite patterns we have seen work well across multiple agencies.

  • Why simplicity? Choosing a web architecture

    on

    If you have ever led or managed a web project, you know that coordinating a team of software engineers is hard work! We hope this blog post can help you understand the concepts behind choosing a web application architecture, so that you can steer your software towards simplicity — even if you don’t have direct software engineering experience.

  • Rapid implementation of policy as code

    on

    No policy or rule stays the same forever. In response to a crisis, policy changes often come much faster, and stakes can be higher.

  • READMEs for you and me

    on

    In software, a README is the documentation that tells you how to start using and understanding a new piece of software. In an organization, a personal README is a way to tell your coworkers how they can best communicate with you, work with you, give you feedback, and support you.

  • Long-term teams, not sudden handoffs

    on

    Don’t let your agency waste knowledge and opportunity. Instead of planning for a handoff to operations and maintenance, plan for a long-term team. Instead of launching your project and then keeping it running, plan for ongoing development.

  • Measuring culture on our engineering team

    on

    To be inclusive and effective, a team needs a culture where everyone is respected, treated fairly, and feels that they belong. We don’t see this diversity, equity, and inclusion work as a “nice-to-have” or optional.

* Some author names have been anonymized.