Vía uno de los muy sabios integrantes (nro tech) de la lista de correo Lista de Soluciones Planeta Mac, una interesante entrada, en inglés, sobre cómo gestiona Apple sus bugs.

Es tan interesante, que me parece que merece más estar en este blog que mantengo sobre cuestiones más profesionales, que en el que mantengo sobre Apple… hay algunas lecciones de como hacer mejor (y no hacer) las cosas.

Origen: Six Reasons Why iOS 13 and Catalina Are So Buggy – TidBITS

  1. Overloaded Feature Lists Lead to Schedule Chicken
  2. Crash Reports Don’t Identify Non-Crashing Bugs
  3. Less-Important Bugs Are Triaged
  4. Regressions Get Fixed. Old Bugs Get Ignored.
  5. Automated Tests Are Used Sparingly
  6. Complexity Has Ballooned

Looking Forward
In an unprecedented move, Apple announced iOS 13.1 before iOS 13.0 shipped, a rare admission of how serious the software quality problem is. Apple has immense resources, and the company’s engineers will tame this year’s problem.

In the short term, you can expect more bug fix updates on a more frequent schedule than in past years. Longer-term, I’m sure that the higher-ups at Apple are fully aware of the problem and are pondering how best to address it. Besides the fact that bugs are expensive, both in support costs and engineer time, they’re starting to become a public relations concern. Apple charges premium prices for premium products, and lapses in software quality stand to hurt the company’s reputation.