This time from the US anti-trust case.
Groklaw: The US-MS Joint Status Report on MS Compliance I think, if it's true that Microsoft is incapable of writing documentation that works when you follow it, we may have figured out why Microsoft can't seem to provide a dependably secure operating system. We're constantly reading about script kiddies and malware authors who seem to be able to invade Microsoft users' computers pretty much at will. This must be the explanation. If Microsoft can't document their own code, obviously it is outside of their control.
Yeah, I guess we knew that; though rarely phrased so cleanly.
Microsoft is developing an approach for new protocols that will incorporate the engineering work for protocol documentation as an integrated part of the overall approach for software product development.
Interesting, insofar as this basically constitutes an admission that they haven't been doing it that way in the past. Indeed, that they are still not doing that now.
(previous post, from the EU case)
PS: I guess the soundbite is the last line in the first quote: If Microsoft can't document their own code, obviously it is outside of their control.
⇦ Driving, mobiles and roleplaying | ⇨ Link: Microsoft will fail - 15 reasons |
