|
|
|
|
|
by shanear
2000 days ago
|
|
These plays can work. Why? Because USDS employees are government employees with escalation paths all the way up to the very top which gives them a lot of power to break down bureaucratic barriers to modern software development that government contractors & consultants would have no chance of doing. They then can bring in contractors to work in the relatively modern shell that they've created. For example, here's a project started by the USDS in 2015. It's responsible for managing the complex bureaucratic process of VA legal appeals. (https://github.com/department-of-veterans-affairs/caseflow) It's open source, continuously integrated and deployed with close to 100% test coverage, deployed on an AWS GovCloud VPC, and was built on a fraction of the budget of similar systems. Active development on this system is now done primarily by contractors now that the relevant bureaucratic barriers were removed. How do we scale this story? More talented people with the desire to serve their country. It's not easy, but it can work. |
|
IMO, USDS makes this worse as someone like Matt Cutts has the cachet to bring in the playbook and get execs to listen. Whereas, I’ve been doing this for 3 years and routinely have to fend off coup attempts as the term “mvp” sounds like a joke to other career employees. As such, it’s often easier to check the box of the federal acquisition requirements and collect a paycheck versus hustling to build a vanilla web app using JavaScript a rest api and Postgres before the checkbox folks shut you down because the baselined version of Jenkins is 5 years old and you installed version 2.26x without a request for change.
So how do we scale this story? Inform politicals and bureaucrats that incentives matter, successful tech start-ups are exception not the rule, sunk costs are real, and you don’t need a catchy name like 18f nor the catchet of celeb dev to right a failing project.