How a 20-year-old kernel feature helped USDS improve VA’s network

Re:How a 20-year-old kernel feature helped USDS improve VA’s... by nostrademons on Friday June 30, 2017 @04:57PM (#14673562)

I think that much of the reason for the existence of USDS is that government agencies like the VA should not be stuck with 10-year-old [1] technology. The idea is that U.S. citizens should be able to expect the same level of technology from their government that they get from Facebook, Twitter, Apple, or Google. They're explicitly trying to change the culture where you do things once for hundreds of millions of dollars and then it's never revisited because the first time was such a clusterfuck.

[1] Actually more like 50 year old technology, if my friends at the USDS are to be believed. In some cases, they're replacing systems where SOP is to manually type in data, print it out, fax it over to another department, and then type it in again to a different system.

[ Parent | on HN ]

Re:How a 20-year-old kernel feature helped USDS improve VA’s... by alexose on Saturday July 01, 2017 @10:44AM (#14677308)

Those kinds of inefficiencies are /everywhere/ in government. They tend to mirror the limited ways departments communicate (see: Conway's Law). Having structured data available isn't a given, nor is the ability to send it across networks that often predate the internet.

I remember an incident where a critical feature went down for days because a backhoe severed the only available link between two agencies. It's hard to overstate how unusual it is by government standards to operate the way modern startups do-- e.g., put everything in the cloud and let Amazon handle your availability problems.

[ Parent | on HN ]