2 ms·
>I don't think any of us working as DoD developers give much of a crap what cloud provider you force us to use The fundamental problem is that you aren't the o
by AndrewKemendo 5y ago
>I don't think any of us working as DoD developers give much of a crap what cloud provider you force us to use
The fundamental problem is that you aren't the one choosing or buying these services. The "people who give a crap" is some mix of political and industrial people with a very light sprinkling of high level program management which are driving the requirements.
So it has nothing - literally nothing - to do with what you as the actual person who is doing the work, want or need to be effective.
This is how the government acquisitions process is written into law unfortunately and I've pushed hard within the government to change that in the past (to some very limited success).
- devonkim 5y agoThe purchaser / decision maker is not the user / practitioner dichotomy exists to a lesser extent in private commercial sector. It’s part of the problems of enterprise software in general
- nonameiguess 5y agoYes. Unfortunately, I'm way too aware of this problem. As far as I'm concerned, it's the biggest problem facing government acquisitions, the fact that any provider's "customer" is always an acquisition office and not its actual users. It's even worse for IC enterprise services, because only your acquisition office has any say in what you prioritize for work and they're the only group of people in the government you're authorized to talk to, but then when you release something, any one of potentially hundreds of external stakeholders can all veto you from going into ops, but you can't solicit their feedback during development.