There are a lot of basic questions I get that inquires about being an MVP. Some of them include:
- What is an MVP?
- How can I become an MVP?
- Are there any exams needed before becoming an MVP?
- Does an MVP get paid?
- Is it compulsory for MVPs to promote Microsoft Technology?
and many more…
To anyone who wants to know more about the above questions I suggest you read the official Frequently Asked Questions.
Today, I want to address the same issue in a different manner. I want to leave the official definition aside, and try to answer the crucial question: “What is really an MVP?”
For me, an MVP is a passionate guy who loves the Microsoft technology and understands it well enough. Well, enough is a very broad, phrase, but it is the reality for virtually all MVPs. Many MVPs have a great understanding of the technology so they help the Microsoft Product team with feedbacks of a certain product and help that product to be enhanced. Many MVPs are extremely good at the technology and work as individual contributors to help develop products. Many MVPs are heavily involved in the Community through helping spread the word. Many MVPs are book authors and blog owners as well, aiming to spread the technology. Lastly, there are a lot of MVPs who are pretty much aware of the technology’s pros and cons. As they understand the limitations of it, they help others to come up with solutions to compensate the boundaries of the technology.
There are many things I can write about, but if you notice there is one common word in all of the above statements. The common word is “Help“. Every MVP is helping someone else to learn, to grow and to create a better ecosystem for technology. The obvious question is that “What is in it for them?” The answer is also very simple: they get what we call time satisfaction. But once in a while, people think that becoming an MVP is also a matter of ego. In the programming world, however, there should be no ego involved. You are here today but you may not be here tomorrow anymore. An MVP has a right to be proud of their knowledge and passion centered on technology, but arrogance is a different thing and must not be a trait of an MVP.
Reading this may make you think that you can be an MVP too, having the burning passion about technology and helping others in your organization at the same time. Great point! Honestly, being an MVP does not stop at only helping others or being passionate with technology. Being an MVP is a commitment to one’s self, promising to keep the standard up and continue the passion onwards. I can keep on writing about what makes a person an MVP, but I do not want to be redundant with what my MVP fellows have already said in their own blogs.
I hope this blog post gives you a clear idea about what is an MVP.
Reference: Pinal Dave (http://blog.SQLAuthority.com)