| ▲ | nomilk 3 hours ago | |||||||
Not to defend the cut or weigh into politics, but how much of 18F was specifically security related? Because that's what's required here, rather than tech generalists. | ||||||||
| ▲ | sandeepkd 2 hours ago | parent | next [-] | |||||||
I cannot comment on the specifics, they change with time. I had few interaction with technologists in one of the federal government body almost a decade ago. Those people were thoughtful, expert with first primitives and open to what you are doing as long as the intent is met. | ||||||||
| ▲ | SoftTalker 7 minutes ago | parent | prev | next [-] | |||||||
Not all outage are security incidents. Most are just technical fuckups. | ||||||||
| ▲ | saagarjha 2 hours ago | parent | prev | next [-] | |||||||
Bad software engineering practices makes security kind of hard to do | ||||||||
| ▲ | riffic 2 hours ago | parent | prev | next [-] | |||||||
There is a well known intersection between reliability and security. Arguably they are two sides of the same coin: https://google.github.io/building-secure-and-reliable-system... GSA's 18F played a major role in applying Site Reliability Engineering (SRE) and modern DevOps practices to federal government infrastructure. | ||||||||
| ▲ | weard_beard 3 hours ago | parent | prev [-] | |||||||
In government security is political. And what we had with 18F was the beginning of a government office that was both tech savvy and politically savvy. Who decides when a DDOS of Trumpcare.gov that is traced back to Akamai servers was an attempt to extort government contracts or “those pesky Chinese state actors”? | ||||||||
| ||||||||