4 ms·

Ah, but you still need to design the tests, which requires knowing the exact design and behavior of the software, which is subject to late change due to tester

by Joeri 12y ago

Ah, but you still need to design the tests, which requires knowing the exact design and behavior of the software, which is subject to late change due to tester feedback. So there is a lot of critical path forming at the end of a software dev cycle which more people cannot pull you out of. The mythical man month reminds us that 9 women can't make a baby in one month. Adding people to a project bound by a critical path can only make it later. And the more you care about design and UX in your initial release, the more you will see that sort of thing.

javert 12y ago
That's true. However, it doesn't really negate my point, it complements it. In this case, Apple could have a "test" that is: install the new OS under test on a machine, and see if performance degrades on other machines on the same network. You could have 10 people test it with 10 different networks. It's expensive, but Apple could heat their HQ by burning cash if they wanted. Admittedly, some things will still get through due to tests that you would only think to do in hindsight. But once you have the test, they won't get through again.