I have several friends who are professional quality engineers in Silicon Valley. For years they have been bemoaning how all companies (not just Apple) have cut or eliminated true Quality Control. Today, these companies use automated tests, not real people with eyeballs on the product. I have no doubt that after this oversight was caught in production, there’s now a new “test case” added to the 'bot for the next release.
I wish this was the case. But the fact that they did the exact same thing with network locations back in 13.0 and still haven’t learned from it almost a year later tells me they also somehow managed to get rid of the one guy who knows how to write the config file for that 'bot.
3 Likes
I blame the culture of “radical disruption”, “move fast and break things”, and “it’s better to ask for forgiveness than permission” that began with Zuckerberg, Musk, and Kalanick and has now spread to pretty much every tech company including Apple. Adding to the problem is that many developers rely on how devices are always connected to the Internet now, making a constant flow of updates and patches possible.
3 Likes
Not just connected, but with high speed connections. Apple, in my experience, is a prime example of this attitude. (But this doesn’t explain interface elements vanishing.)
1 Like
Yes indeed! I would love for iOS apps to be better behaved when network throughput is poor. Mail is really bad in that aspect. And Mail actually even has a refresh button. The same can’t be said for Notes or Calendar.
1 Like
Yes. And I do think that the Keep Shipping™ mentality causes interface elements and other things to vanish because it’s assumed that anything that is done incorrectly or sloppily or that is not re-enabled after being “temporarily” turned off can be quickly fixed in the next update. Speed, not quality, is the objective these days.
1 Like
David Shayer wrote an excellent article about why iOS 13 and macOS Catalina were so riddled with problems. Apple improved things in subsequent releases.
1 Like