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.
Alex Yale-Loehr is a software engineer working with the Digital Service at the Veterans Affairs team.
- Health Tech Sprint Aims at Improving Care Access and Experience
- GSA Steps Up Security for .gov
- A Design Challenge to Improve How School Data is Reported
- Want a More Innovative Agency? Encourage Employees to Experiment
- Collaborating for Better Design, Technology, and User Experience