![]() A team of senior managers to coordinate all these people, write the cheques, and justify the costs to their Vice President.Twenty-five translators to translate the documentation and error messages into all the languages supported by Windows.The managers for the translators live in Ireland (European languages) and Japan (Asian languages), which are both severely time-shifted from Redmond, so dealing with them can be a fairly complex logistical problem.One documentation manager to integrate the new documentation into the existing body of text, update tables of contents, indexes, etc.One copy editor to proofread the documentation.One technical reviewer to proofread the documentation.One technical writer to write the documentation.Three or four testers to participate in an ad hoc bug bash.One tester to write the test cases and add them to the nightly automation.One test lead to update the test schedule.One PM to add the security model to the specification.At least one dev, tester and PM to brainstorm security vulnerabilities.One usability expert to review the specification for accessibility and usability issues.One localization expert to review the specification for localizability issues.One program manager to write the specification.One dev to spend five minutes implementing ChangeLightBulbWindowHandleEx.But how many Microsoft employees does it actually take to change a lightbulb? ![]() I'd always tell these people the same thing - if it is only five lines of code then go write your own ActiveX object! Because yes, you are absolutely right - it would take me approximately five minutes to add that feature to the VBScript runtime library. ![]() This link gave me perspective on what it costs to implement a single feature at Microsoft:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |