MS Openness and MVPs/RDs/trainers/authors...

Microsoft Openness?

Randy Holloway's Weblog — Fri, 30 Apr 2004 04:02:00 GMT

re: MS Openness and MVPs/RDs/trainers/authors...

Steven Collier [MVP] — Sat, 01 May 2004 21:42:00 GMT

As an MVP I find your query quite bizare. The implication that MVP's might see a downside in the 'insiders' talking publically is weird, I certainly don't see my MVP award meaning I'm a go between, and any credibility does not come from inside knowledge. At the moment we infrequently get allowed access to NDA material, but this is totally useless, disclosing stuff is what we do.

Where I think MS Product teams miss on opportunities is in using MVPs as sources of information INTO your product teams. We are generally geeky rather than businessy, but the community has a huge insight into using your products in the real world.

re: MS Openness and MVPs/RDs/trainers/authors...

Chris Garty — Thu, 06 May 2004 05:18:00 GMT

The new openness is excellent for everybody. I can't see any downside other than competitors being able to keep up easier. But Microsoft has such great momentum that I don't see that as a problem.

Just keep incresing the frequency of the previews. Doing so allows solutions providers to ramp up even before the official release.

Be sure to check out how the guys at JetBrains run their EAP for ideas (http://www.jetbrains.com/resharper/) :)

- Chris

re: MS Openness and MVPs/RDs/trainers/authors...

Mark Cliggett [MS] — Fri, 07 May 2004 02:56:00 GMT

Steven: I agree on the point about doing a better job pulling info into the product teams from MVPs. We are inconsistent on that - some teams do better than others. But overall we can all do a lot better.

Sorry to ask bizarre questions :-) What I'm doing is extrapolating out to a time when all customers have clear mechanisms for providing feedback/input throughout the cycle, and we're doing a good job being responsive to that input. (Admittedly, that's a ways in the future.) In that world, what extra things should we be doing for MVPs? Raising the bar higher on what we do with their bugs/suggestions (e.g. if it's a marginal fix/postpone, maybe we just fix it because it is an MVP - and track to ensure that fix rates for MVP-submitted bugs are at least as high as for bugs coming from the public). Responding faster? Giving them very clear escalation paths and encouraging free use of them?

The basic question is "what do you want more of, and if we give that those things to the public, are there still more things?"

Chris: Thanks for the pointer to jetbrain - it's at least the 2nd one. I'm going to go look now.

VB.NET 2005 feedback

Amr Essam — Sat, 15 May 2004 10:26:00 GMT

I develop with both C# and VB.NET, but I like VB.NET to be better because I am old VB developer.
I just installed VS.NET 2005 (Technology Preview), and this my prompt feedback

------------------------------------------------------------------------------
I surprised that I found productive feature in C# and not
in VB.NET, this features:

1) Refactoring
I tried Refactoring in C#, It is really very productive
feature.

2) IntelliSense/Auto Completion (Keywords)

Now only in C# debugger feel the Language keywords like
(private, public, foreach ...), and auto complete it to
you.

However VB.NET have longer Keywords such as (MustInherit,
NotInheritable,.)

----------------------------------------------------------------------------
I dreamt that I can find these features in VS.NET, but
unfortunately I frustrated when I found this feature in C#
not VB.NET ?

Microsoft always say that it concentrate on Productivity
features in VB.NET, How does VB.NET 2005 lack these
very productive features ?!

Looking forward for your reply.

Amr Essam
www.Verizon.com
Consultant & Team Lead
MCSDT + MCT
Dallas, Texas

re: MS Openness and MVPs/RDs/trainers/authors...

Steven Collier [MVP] — Fri, 21 May 2004 00:55:00 GMT

My personal opinion is that we MVPs take information that is publically available and use it to help our fellow customers with their issues. In many cases we can bring real world experience and opinion, unfettered by what the correct thing to say from MS would be.

Also remember the MVP award is retrospective, there are plently folk answering questions and helping others who have not been awarded yet, they require the same level of access to material as MVPs.

You are correct that the interaction from product groups is patchy, my speciality really seems to keep us at arms length, while others engage in a great level of dialog. I do get annoyed when a service pack gets released and the like without them even send us a message to let us know about it. The first we hear can be when someone asks about it in a news group.

There is a bigger and more important issue around the early release of code and how this effects MVPs ability to help customers of released products through the appropriate newsgroups. When SharePoint 2 was released to public preview there was no route provided for discussion or comment, so the newsgroup was packed with people asking V2 questions, my personal knowledge was about 6 months short of being able to help.

I don't know what gain MS get from these preview releases, but to me it's not worth it.

Mark Cliggett s WebLog MS Openness and MVPs RDs trainers authors | Quick Diets

Mark Cliggett s WebLog MS Openness and MVPs RDs trainers authors | Quick Diets — Tue, 09 Jun 2009 14:16:00 GMT

PingBack from http://quickdietsite.info/story.php?id=9305

Mark Cliggett s WebLog MS Openness and MVPs RDs trainers authors | Joint Pain Relief

Wed, 10 Jun 2009 03:04:07 GMT

PingBack from http://jointpainreliefs.info/story.php?id=2007