Update VS Help documentation - new qualification for MVP?
-
Yep, having another frustrating moment of crappy VS/.Net HELP. So here's a suggestion, add to the mysterious MVP criteria "fix up 100+ items on the MSDN Library every year" and make it a requirement. Ya, no proof, no MVP. And they have to start with those that are in-accurate, incomplete, and not telling you how or why you need to use the dang method/property/etc. If they are lucky, they'll finish before the US cleans up it's deficit.
-
Yep, having another frustrating moment of crappy VS/.Net HELP. So here's a suggestion, add to the mysterious MVP criteria "fix up 100+ items on the MSDN Library every year" and make it a requirement. Ya, no proof, no MVP. And they have to start with those that are in-accurate, incomplete, and not telling you how or why you need to use the dang method/property/etc. If they are lucky, they'll finish before the US cleans up it's deficit.
It's a great idea, but sadly I fear it would be a task of the type that would make Sisyphus say "I give up" as MS continues to churn out inferior documentation for an ever expanding stream of product releases.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
Yep, having another frustrating moment of crappy VS/.Net HELP. So here's a suggestion, add to the mysterious MVP criteria "fix up 100+ items on the MSDN Library every year" and make it a requirement. Ya, no proof, no MVP. And they have to start with those that are in-accurate, incomplete, and not telling you how or why you need to use the dang method/property/etc. If they are lucky, they'll finish before the US cleans up it's deficit.
Tim Schwallie wrote:
If they are lucky, they'll finish before the US cleans up it's deficit.
Sadly, they have plenty of time to get on this.
-
Yep, having another frustrating moment of crappy VS/.Net HELP. So here's a suggestion, add to the mysterious MVP criteria "fix up 100+ items on the MSDN Library every year" and make it a requirement. Ya, no proof, no MVP. And they have to start with those that are in-accurate, incomplete, and not telling you how or why you need to use the dang method/property/etc. If they are lucky, they'll finish before the US cleans up it's deficit.
So you're giving them an infinite amount of time?
-
Yep, having another frustrating moment of crappy VS/.Net HELP. So here's a suggestion, add to the mysterious MVP criteria "fix up 100+ items on the MSDN Library every year" and make it a requirement. Ya, no proof, no MVP. And they have to start with those that are in-accurate, incomplete, and not telling you how or why you need to use the dang method/property/etc. If they are lucky, they'll finish before the US cleans up it's deficit.
Tim Schwallie wrote:
And they have to start with those that are in-accurate
Like by removing inappropriate hyphens? You can't buck Skitt's Law.
I wanna be a eunuchs developer! Pass me a bread knife!