I implement ERPs for a living.
I am currently implementing a system that will have 10K users, with a highwater mark of 50K or so.
We have 6 test cycles, including several full-blown performance tests.
If I was to put together a plan for even this small implementation that had 2 weeks of testing would get me and my entire team fired on day one of the project.
This is like children being given a gun and then complaining when people get hurt.
I HATE it when I have to deal with children in my industry.
I have been doing this for 35 years and it never ceases to amaze me that when we left mainframes we also left mainframe disciplines.
One thing we can all be sure of. There were people who knew that this turkey(website) would not fly. The technical people would have known that these problems were there all along. To go live was strictly a political decision.
One has to wonder how many Americans this administration is willing to kill in order to achieve a better(Progressive) America.
Roger that. Loudly and often. There's no small irony, too, in the "new" popularity of the thin-client or web client all tying back to a massive server infrastructure. We've come full circle again. It's fair to observe that today's web interfaced server systems are orders of magnitude more complex than most anything in the big iron days of mainframes and dumb terminals. But like Gall's Law says... It would have been better to add sophistication to the simpler system that worked than it has been to jump full-function into a system of near-biological complexity.
Yes, to say noting of the complexity of having to interface with antiquated gubmint systems from IRS, Social Security, HHS, Immigration, CMS and hundreds of insurance companies... you can’t test this bitch enough.