4 ms·
More constructive questions: How would you change Apple's development process to have caught this bug, and bugs like it? Do any of you have processes in place
by jimbokun 17y ago
More constructive questions:
How would you change Apple's development process to have caught this bug, and bugs like it? Do any of you have processes in place for your companies that would catch bugs of this sort?
Sure, you can always add a test for this specific bug, but catching other bugs like it? Anyone have positive bug catching stories to tell?
- fauigerzigerk 17y agoMaybe it would help to prioritize unit tests and code reviews. Code that deletes users' data permanently deserves more eyeballs and testing. Just an idea. I never tried it.
- oscardelben 17y agoI think this bug is only a side effect of something bigger behind, where the chances of testing could be higher.
- ajg1977 17y agoApple need to move away from their current approach of seeding betas/RC to select developers and towards the open beta testing that Microsoft have successfully embraced in recent years. As the number of users and potential hardware/software configurations continues to grow they cannot expect to cover a respectable percentage of scenarios with their current closed approach to testing. See also MobileMe Launch.
- xsmasher 17y agoScuttlebutt is that an early developer seed may be the cause of the problem - so if more people had used that seed, this would have been caught sooner. Of course more people would have been hit by the bug.