twincruisers
I love it when a plan comes together
- Joined
- Jun 15, 2021
- Messages
- 413
This is my question too. But I don't think they can actually test it without having masses of people test it at once. Therefore, it will seem like they just bam, drop it on the guests one day.
Realistically they only way to do this would be to do simulated tests but not with actual people in the park. The problem with that though is that as good as we've gotten at AI and machine learning, people are not machines and we have biases and weird decision making tendencies. Programs still have to be programmed, and it's REALLY hard to predict human behavior. The whole thing is very fascinating to watch develop. In theory it's interesting. But it's really messing with my vacation plans. To the point that we are considering moving our trip until it settles out.
Standard software testing is to start with internal developers, then alpha test in the QA department. Then Alpha 2 with a few trusted individuals (few choice clients/trusted partners), then a beta with a few hundred (to a few thousand) select customers, repeat as needed. Maybe one more beta to simulate millions of connections to ensure scalability is working correctly, then finally a release version. That said, we seem to skip to Alpha to the general public (General Availibity Release) pretty quickly now to iterate quicker. Once you can confirm you're getting good consistent data from the base software, then you can really turn on the ML/AI algorithms to do their thing.
But I do agree, waiting to let the bugs and ML/AI stuff do get up-to-snuff is a good idea vs being a genie pig.