4 ms·
Re: Microsoft and testing Perhaps things have changed now, but previously MS had a setup with 2-4 testers per one developer whereby latter would churn out code
by eps 14y ago
Re: Microsoft and testing
Perhaps things have changed now, but previously MS had a setup with 2-4 testers per one developer whereby latter would churn out code as fast as he can (of a respective quality) and testers were expected to identify critical bugs so that the dev can plug them, in the same speedy manner as he'd code the original. I had few close friends work for Microsoft in the 90s and the impression I formed after chatting with them was that the MS products routinely were something that was hacked and hammered into a state of not crashing too frequently. So while Microsoft might have a strong focus on testing, it was used to be completely misplaced and misguided.
- epo 14y agoA focus on testing is not the same as a focus on quality. Also, if your test criterion is "doesn't crash" then a lot of slowness, resource leaks etc, may be, and probably are, acceptable to you.
- timtadh 14y agoMy impression is the Microsoft of the 90s has little to do with the Microsoft of today in terms of QA, testing, and security. This impression is "secondhand" (I have never worked for Microsoft). Reforms were made, so if you information comes from the 90s it may be time to update it.
- city41 14y agoAll MS info should come with a grain of salt from the simple fact it's a company of about 90,000 people with thousands of unique teams. I worked at MS and every team I interacted with handled testing and QA very differently.