That's the excuse you hear from all sloppy developers. There is no excuse, ever, for bringing a system live that is functioning as poorly as AC appears to be right now. It's done all the time, but it's the wrong way. I've been over IT departments that did a lot of developing and never tolerated it. Never had to. I had the right people and the right systems.
In my working days, I developed two pretty big database programs that were used by dozens of people to track and report important business information.
Once I thought I had it right, I logged on as a regular used and tried every function before I let it go public. That's just common sense because many people are looking for you to fail. Don't let it happen because they will never have confidence in you or your programs again.
Both of those are correct, but then there's real world.
I managed some mega-$$$ projects (approaching a quarter-billion $$ budget on one of the systems), and our teams mostly got things right the first time. And then we tested the systems to death... and found boo boos. Not sloppy developers at all, but we were inventing stuff that had never been done before, for users who were "envisioning" system they needed for mission. Fixed those boo boos, tested to death again, found more boo boos.
Fixed those, released the beta version with a few power users, and they did "stupid stuff"... outside design parameters... because they needed the system to do that stuff and hadn't quite expressed the requirement perfectly in the first place...
So we fixed that... and the system worked pretty well... except for those pesky new requirements that kept pouring in because mission demanded it.
Lots of moving parts, mobile teams, world-wide users, evolving mission... the dart board moved... and the budget is often the budget.
So yeah, errors should never occur.
But they do.
We also found some of the users didn't like some of the interface implementations. At the same time, other users loved those same bits and pieces. Well, we couldn't please everyone, nor did we care to try. As long as the product met the goal (got the user the answers, historical detail, and predicted way forward he needed... all as quickly and efficiently as he needed it) that at least was measurable. The "I like it" factor was often too subjective to waste much time (and $$$) with.
I haven't looked at the new AC interface, but that's partly 'cause I seldom used the original website interface anyway... but even if it sucks, feedback to the developers is appropriate, and they'll eventually get it mostly right. Good developers, bad developers, great work ethic, slop, whatever... No sense wasting any emotion over it.
-Chris