James Whittaker explains why Ms software is so bad after so many tests

See: http://blogs.msdn.com/steverowe/archive/2008/10/02/james-whittaker-on-why-ms-software-sucks-despite-our-testing.aspx

A friend showed me an article written by James Whittaker.Article. I don't know that JW has opened a blog, so I am very happy after reading it. He wrote a lot of interesting things about the test, so if you are interested in the test, I recommend you also read it (there is a link on the left ).

Ms claims to be highly tested and is proud of this. This inevitably leads to a problem: If ms is so good at testing, why is your software so bad? James Whittaker once asked this question. He is currently working in MS, so he is in a good position to try to answer this question.

James basically gave three reasons:
1. Ms software is very complex. Windows, exchange, office, and so on are all very large projects.
2. Many people are using MS software. Eric Raymond once said that if there are enough people to focus on it, all bugs will be invisible. If this applies to open-source software, it also applies to closed-source software. In the first few days of Ms's release of new software, millions of people will use it. Hundreds of millions of Windows installations. With so many people using it, any bug may be encountered.
3. Ms testers are not involved early enough in the entire development process. Of course, different departments in the company may be different, but in general, there is still much room for improvement.

Published Thursday, October 02,200 8 am by steverowe