|
|
|
|
|
by jbooth
4491 days ago
|
|
You're not wrong, but anyone who actually has an office in the physical whitehouse, or anyone within, say, 5 layers of the President, actually shouldn't be concerned with the implementation of the technology. They should be focused on getting money and resources to the people who do the tech and running interference for them to help prevent them from being sabotaged by political opponents. In between their other million non-technical job responsibilities, many of which involve a lot of legal, policy and political details. That said, obviously they should have brought in the campaign website team to oversee this instead of doing the standard federal government contracting route, which leads to a late, over-budget project literally every single time. |
|
That's called cronyism, and, for the most part, it's either against the law, or will get you destroyed in the media. One of the biggest challenges in government is that, for those of us in startup-land, the process goes something like: "I need to hire someone, I'll call my friend who I know does good work". You can't really do that in the government, or everyone who isn't your friend won't be happy.
The standard federal contracting route is certainly a mess as well. The underlying belief that everything can be reduced to a series of checkboxes, and whoever can check the boxes the cheapest wins leads to a disaster.
Hopefully, one of the outcomes of all of this is we rethink how the government software (and other sorts of procurement) process is done.