Until this new Amtrak site is fully functional, without bugs, why can't they simply revert to the old site which worked reasonably well?
At my company, we go through something like this with our intranet every time it undergoes changes--some of those significant, involving a new OS. There is ALWAYS the option to back out of the "new" and temporarily go back to the "old" until the "new" is proven through exhaustive testing to be ready for prime time. This has actually happened more than once, unfortunately. Is this beyond the Amtrak IT department's capabilities?
I really hate when software developers unleash a Beta version to the public sphere so real-world users can do the developers' job of discovering bugs. I know some computer nerds will disagree, claiming a new system can't be fully evaluated unless thousands of simultaneous users are in queue. Bull! There is a software solution to simulate thousands of users without infuriating the public.
That is sort of what happened when the original ACA website was launched. That is part of the reason the ACA never reached its full potential. Now Amtrak? Exasperating!
Edited by Skyline, 09 October 2017 - 10:33 PM.