Originally Posted by
gabrielz
PS - another thing that would help is if we had confidence in UA's tech team to write good, clear code.
You're right. It's snowing and I'm have already broken into the holiday cocktail stash. Writing code is the scary part! Even if they have requirements and a documented process, it may or may not take into account all edge cases and short of talking to the developer(s), the people at UA that would respond to us probably don't even know. It could easily be that this is our "process" BUT there are these 10 exceptions, but the cost/benefit to fix (having to make adjustments in other parts of the system) are not worth sorting out. Short of reading the requirements doc and infrastructure comments you wouldn't know. Fine line between "bug" and undocumented feature sometimes ;-).
That said, I kind of like the changes and would prefer UA wait until as late as possible to clear upgrades. Most of my travel is for work (usually not more than 10 days notice). This tends to be put me as a 1K on high fares. I've been pretty successful on upgrades this year. It actually works to my advantage to sort the list based on status/fare, no companions, etc.
Now, when traveling with my 3P SO... the opposite is true. I'd be happy with NC9 and C=0