Sorry, I was introduced to "dogfooding" in Dreaming in Code. I believe there was even a chapter named after it and it was a pretty big deal about how you dogfood to maintain quality. So when I hear the term that's what I assume is implied.
For most day to day usage issues, dogfooding is a great way to hammer out issues. Will they find issues with every use case? No, but they will find some. Also, generally, the more diverse and large the organization, the more use cases will be dogfooded (assuming the bulk of the org is encouraged/required to do so).
When you are talking a company of 90k+, encouraged dogfooding will hit a lot of different use cases.
And you are correct.
I remember back in the day (2005) reading about MS employees hiding their ipods when they were on campus:
http://www.wired.com/gadgets/mac/commentary/cultofmac/2005/0...
And then Steve killed everybody's buzz by banning Apple products entirely:
http://www.cultofmac.com/155131/microsoft-bans-employees-fro...
My point regarding 9 is that the developer tools are buggy and painful to use compared to chrome. As a web developer, you would want them fixed as soon as possible.
There's something of a culture of "our internal developers are smarter than our external developers" at Microsoft, so dev tools are often where the dogfooding has been the weakest. It comes from having internal developers who are hacking on things like OS kernels while the external developers have a massive population of coders churning out enterprise CRUD forms (along with a smaller population of more advanced developers), but this internal/external tool gap sometimes really bites them.
Interesting. I didn't get that impression across 4 teams, either as a PM intern or a FTE dev.
Like I said, I might be misreading things. And certainly the blogging community around their dev tools has improved the level of detail that goes out to developers committed enough to keep up with them.
See, I've always assumed the exact opposite based on how rough the user experience is on so many Microsoft products.
I've often wondered if it was possible for a web developer at MS to sit down with IE for 30 minutes and not think "I have to fix this.... now!" When I realized how awesome Chrome developer tools were I never wanted to go back. But of course, as a web developer, you have to go back.
Or maybe that is the problem. Maybe too much dogfooding blinds you to how great the competitor is.