3 ms·
Nevermind all that. My comment was purely targetted at the text I quoted. I just meant that saying "my online system sucks and you shouldn't care (or should be
by dkersten 16y ago
Nevermind all that. My comment was purely targetted at the text I quoted.
I just meant that saying "my online system sucks and you shouldn't care (or should be complacent) because its just a hack on top of some legacy system" isn't an excuse you should accept.
Just because you do not feel its worthwhile to replace the underlying system (and I'm not arguing over whether it is or isn't), doesn't make it alright that the end result is bad and certainly does not mean people should accept that reason as an excuse.
- rdl 16y agoI agree it isn't ideal, but given limited resources, there are a lot of cases where having a good manual/human exception handling procedure is a better solution than fixing the software. (And training employees to "be nice to customers, pretend your boss's mother is flying today" would improve all interactions with the airline; fixing this one particular bug wouldn't be as generally beneficial. Realistically United will do neither :)
- dkersten 16y agoI agree with what you're saying, but I still can't help but feel you are missing the point I wanted to make (or perhaps you didn't miss it and simply wanted to add to it to tie it back to the article, in which case I apologize and you should feel free to ignore me). Somebody made a judgement call and decided that X was more cost effective than Y. Somebody else is inconvenienced by this decision and complains about it. Saying that the complaint is invalid because X is a dirty hack is not, IMHO, a valid excuse. Saying (as you have) that it was decided that X was more cost effective than Y and that is why X was chosen is a valid excuse. The only reason I'mpushing the point is because I hear those kinds of excuses all the time, applied to all sorts of things.