4 ms·
The basic set of requirements are the easy part. It’s when you have to account for the differences between each state (50 factors!) is where the software becom
by xyst 7y ago
The basic set of requirements are the easy part.
It’s when you have to account for the differences between each state (50 factors!) is where the software becomes O(n^n) complex over the development of this product.
Even the best private companies struggle to build similar systems for a single entity.
I think each state should be accountable for their own programs. Avoids the “single point of failure” issue as well.
- imtringued 7y agoThere are still benefits to choosing the same ecosystem. If everyone uses Java or Go and the same web framework then they can invest money into libraries that are useful for all 50 states. I've been at organizations that simply decided to use the same stack as another state (not USA). You end up using the same plugins and libraries. Even if you choose the wrong ecosystem because it is not mature enough you can just build it yourself and everyone benefits.
- prirun 7y agoThe problem is, you have to get the politicians to agree to the same policies so that the code works for both states. Politicians don't like to be told "You have to do it this way because of the computer system". Politicians want to decide the rules, then make everyone follow them. They don't follow rules themselves.