← Back to context

Comment by danso

9 days ago

What's especially unfortunate is that experienced USDS employees had already achieved the one software engineering task that is basically impossible for a 19-year-old (or a newly hired USDS employee of any age): convincing a federal department manager that using a static website is a great solution — nevermind also publishing all of its source code and documents on a public github.

USDS really did represent the best of the federal government. They modernized hundreds of websites, brought accessibility and mobile access to the forefront, improved usability, and a lot of that work is invisible, slow, internal politics/battles.

Understandably everyone is upset about what "DOGE" is doing. But on top of those harms, the killing of USDS (or at least ending its core mission) is also a real harm.

  • I'm not a federal contractor nor employee, and I am a die-hard Pivotal zealot, so absolutely take the following with a grain of pink Himalayan rock salt:

    Although overshadowed by Kubernetes elsewhere in the industry, I suspect that Pivotal's Cloud Foundry Platform as a Service (PaaS)--which the US General Services Administration's (GSA) internal digital transformation consultancy, 18F, adopted[0] in 2015 significantly influenced the software delivery philosophy of the federal government by making trivial heretofore disastrously cumbersome provisioning, staging, and deployment processes. The step away from hand-provisioned virtual machines to elastic, accommodating environments may have made agile development possible in federal offices, bringing our government into the 21st century, only fifteen years late.

    I distinctly remember the switch from "here's your VM" to "here's my code," and--as an application developer--I never want to go back.

    0. See: https://cloud.gov

    • To me, that's the most important goal of devops tools teams in practice:

      "Internal team, what's your current greatest pain point?" -> Make that easier / faster / better

  • [flagged]