When an experiment with existing technology does a “good enough” job
1–10 of 95 posts
Re: When an experiment with existing technology does a “good enough” job
#2Re: When an experiment with existing technology does a “good enough” job
#3The cost comes from compliance, audits, paperwork. Trials, PoCs, etc.
You also need to prove security and a long term lifecycle for the solution. Those open source packages - are they being updated? Who validates patches? etc etc.
Those are moats, once you're able to deliver the above, you're set for a long time.
Good luck!
Re: When an experiment with existing technology does a “good enough” job
#4Not that I'm saying $86M is justified - rather that I can start to see how things might add up.
Re: When an experiment with existing technology does a “good enough” job
#5Well, if we're just checking to see if a car is registered stolen, that's hopefully a very small database. A simple hash table should be sufficient for a yes/no decision. But God only knows what goes on inside the DMV, and getting that data out into a rapidly queryable state could be tricky.
Re: When an experiment with existing technology does a “good enough” job
#6Obviously complicated requirements exist but I think there's a way of embracing this with some skilled workers
I think that the digital service is trying this a bit
Re: When an experiment with existing technology does a “good enough” job
#7Any project in a heavily regulated environment is not measurable that way. The cost comes from compliance, audits, paperwork. Trials, PoCs, etc. You also need to prove security and a long term lifecycle for the solution. Those open source packages - are they being updated? Who validates patches? etc etc. Those are moats, once you're able to deliver the above, you're set for a long time. Good luck!
Re: When an experiment with existing technology does a “good enough” job
#8Re: When an experiment with existing technology does a “good enough” job
#9Any project in a heavily regulated environment is not measurable that way. The cost comes from compliance, audits, paperwork. Trials, PoCs, etc. You also need to prove security and a long term lifecycle for the solution. Those open source packages - are they being updated? Who validates patches? etc etc. Those are moats, once you're able to deliver the above, you're set for a long time. Good luck!
Re: When an experiment with existing technology does a “good enough” job
#10I feel like there's a killing to be made in "bidding for government contracts as a service". Plus you'd be doing A Good Thing (at least in theory) Obviously complicated requirements exist but I think there's a way of embracing this with some skilled workers I think that the digital service is trying this a bit