I continue to think they should have worked out all the bugs in this system before going live with it.
If this was the case with all software, you'll still be writing with a typewriter and mailing letters to keep in touch. As someone who worked as a software tester, I can tell you it's just about impossible to think up all the ways software can fail or just be a little off. It largely depends on those who design the software and those who program it (and it should never be the same person). It also depends on the contract. If the software was to be delivered on a certain date, it was. Only Microsoft and the like can get away with delaying new releases.
As a tester, one is pretty much restricted to what the designer has outlined. If the designer didn't design for your problem, it didn't get programmed or tested. If it was noticed, it will be either designed and programmed and tested as a patch, or as a feature in the next version. The turnover for changes can be swift or a long time coming. If the problem is life threatening or involves personal finance, the change happens quick (or should). If it is not life threatening, well, it might get changed if it is a problem for enough people. It also depends on the user; if the MTA doesn't think it's worth reporting, they won't.
no subject
If this was the case with all software, you'll still be writing with a typewriter and mailing letters to keep in touch. As someone who worked as a software tester, I can tell you it's just about impossible to think up all the ways software can fail or just be a little off. It largely depends on those who design the software and those who program it (and it should never be the same person). It also depends on the contract. If the software was to be delivered on a certain date, it was. Only Microsoft and the like can get away with delaying new releases.
As a tester, one is pretty much restricted to what the designer has outlined. If the designer didn't design for your problem, it didn't get programmed or tested. If it was noticed, it will be either designed and programmed and tested as a patch, or as a feature in the next version. The turnover for changes can be swift or a long time coming. If the problem is life threatening or involves personal finance, the change happens quick (or should). If it is not life threatening, well, it might get changed if it is a problem for enough people. It also depends on the user; if the MTA doesn't think it's worth reporting, they won't.