Originally Posted by
wlau
I work with developers ALL DAY LONG! Good ones would bring back to product manager better options/suggestions, and even tell you why. Product Managers both internal or external (if outsourced) don't often know very low level details or how to articulate sophisticated technical terms. The fact is the API exist, and being used by Delta's competitors and other places like Starbucks and Walmart apps, it's enough to give you a clue how prevalent it is. For example, do you think it's right or fair to expect Product Manager to tell you which memory read/write API to use or what stream open APIs to use? I am sure Delta's product manager would have some lingo or spec to the tune of "... ensure the barcode is properly displayed, regardless of screensize, and that's easily readable by all Delta barcode scanners..." The easily readable phrase would sufficiently necessitate the use of such API to brighten the screen when the barcode is displayed. There are things that are so basic, it doesn't even warrant a callout in the spec.
In shops where employees are doing the work, you get much more collaboration and technical enhancements delivered. In shops where you outsource development, have a set fee you are paying to get documented features delivered...not so much.
I don't have knowledge of how DL staffs the particular product(s), I was merely noting that the failing is not necessarily just a failing of some sub-optimal developer.