When people think of government software, they often think of COBOL and PowerBuilder 5, with manual software deploys every three to six months on a fixed number of machines in a government-run data center. This perception is sometimes justified, but sometimes entirely wrong. Regardless, the perception makes many developers reluctant to work for the government because they worry about the frustrations of getting stuck in the bureaucracy instead of being able to iterate rapidly, ship products, and deliver value.
Raquel Romano is a software engineer working with the Digital Service at the Veterans Affairs team.
- Presidential Innovation Fellows Join FDA to Advance Digital Health
- Introducing USWDS 2.0
- Web Analytics: Why the Users Metric Just Got More Complicated
- Q&A With Ryan Day About GSA’s API Strategy
- A Year in the Life of a PIF
- Innovative Approaches to the Opioid Crisis — April 30, 8am ET
- Government UX Summit 2019 — May 15, 9am ET
- DAP Learning Series: Using the analytics.usa.gov API — May 23, 2pm ET