So much for a smooth transition from one device to another. Apple, you let me down! All told, four to five hours of work to get my phone to work as expected, more to communicate the problem to the company. And from Apple... the sound of crickets.
But at least now everything once again "just works", at least, until ...
This is the Banana Philosophy of product development. The product is designed to ripen at the consumer's. A manager for Storage Technologies at IBM recently traced this mentality to the invention of the EEPROM, the Electrically Erasable Programmable Read Only Memory. The successor to the EPROM had the advantage of being reprogrammable without having to be removed from the device. If a device's EPROM contained an error, the whole device had to be recalled. In order to avoid this, programs were tested as thoroughly as possible, perhaps even more thoroughly than normal programs. A buggy program in an EEPROM, on the other hand, could be corrected on site. Bringing a product to market before the competition became more important than testing it for bugs, all of which would never be discovered anyway, Marketing claimed, no matter how much testing Engineering did. Today, this philosophy of non-testing is routinely applied to program development in general, no matter whether the program resides in EEPROM or in external storage. There is even some evidence that it is being applied to hardware as well, e.g., anorexically thin mobile devices that bend when sat upon, delaminating display screens.
I suppose the only solution is to refuse to pay to test and wait until neophiles give the all-clear.
