I was pleasantly surprised last week to hear that Microsoft awarded me an MVP (Most Valuable Professional) for my work in the community with ASP.NET MVC.
Thank you to everyone who nominated me, and all the community members who tried not to fall asleep during my presentations and talks ;)
And now for the official logo...
One of the most interesting things about being an MVP is participating in the MVP Global Summit. It's a chance to meet other professionals from around the world whom are passionate about finding the best way to use Microsoft tech to get the job done. Looking forward to attending early next year.
Now that I've basked in all this honor and glory, on to the real content of this post...
Does MVP = Microsoft fan boy? No - at least not from what my discussion with Simran Chaudhry, the Microsoft employee in charge of the program in Canada. Since it's a Microsoft sponsored program, there is a code of conduct that is expected that sums up to basic professionalism.
MVP doesn't mean you're singing Microsoft's praises and pushing product. You're free to disagree with Microsoft tools/frameworks, etc from a professional point of view - the key is to be professional about it.
Example - it's well known to many of my colleagues that I feel Subversion is superior to Team Foundation Server when it comes to source control. Having used both on different projects, Subversion is faster for checkins, updates, and merges. Also, Subversion is a lot easier to use when the server goes down or you're working remotely in a disconnected state, like when you're on an airplane for example.
However, I realize that a lot of corporate environments use it for MORE than just version control (i.e. issue tracking, project workflow, continuous integration even). I learned this while working for the Enterprise Architecture department for a client last summer. There is more to tool choice than just what the developers finds best. Yes, the world doesn't revolve around us.
So while I'd rather use Subversion (or Git if you're a cool kid) there are advantages to TFS from an Enterprise Architecture point of view, like looking at critical bugs raised across the 80 projects running at your company. I also know that TFS 2010 is way better than 2005, so Microsoft is improving their game. Maybe in 20xx TFS will be on par with Subversion for source control?
In the end a healthy debate and feedback to Microsoft will ultimately help them make better products that serve their customers. This is another core part of the MVP program, being a channel from the community back to the Microsoft product teams.
Even open-source contributors make a profit - look at JBoss or Firefox! My friend Clinton Begin didn't make millions off iBatis, but he certainly helped his career along by doing it. That might not be their primary motivation, but it certainly is an outcome. Do you think that Linus Torvald will ever have a problem finding a great paying job? I say - good for them! They're helping the community while helping themselves.
So ends my rant. Please post comments if you disagree :)