Year 10 as an MVP – Adding The Azure Expertise

[Image Credit: Microsoft]

Today was a stressful day – it was the annual date of my MVP renewal. The program has changed quite a bit in the last year, and this is the only renewal date from now on, so you might have seen more MVPs than usual sharing their nerves online.

I was extremely nervous, especially because my profile on the MVP directory went offline. I was sure that I was a goner. But later in the day my profile re-appeared, with a change.

NewMVPStatus

To mark year 10 as a Microsoft Valuable Professional, I have been awarded with a double expertise:

  • Cloud & Datacenter Management (Hyper-V)
  • Microsoft Azure

And a little later in the afternoon, the notification email arrived:

MVP2017Email

My eldest daughter, who is 10 years old, had noticed my stress and wanted to congratulate me. I was banished from the kitchen and later I was presented with this cake – I’m a proud Dad:

MVP10Cake

 

These are fun times ahead for IT pros. My double status, with on-premises virtualization and public cloud, mirrors what’s going on in many of our careers, either already or pretty soon.  My career has changed so much over the years:

  • UNIX programmer
  • Have-a-go-hero Windows consultant
  • Re-inventing myself to be a better Microsoft engineer
  • Senior sysadmin in an international company
  • MVP in SCCM
  • Virtualization engineer
  • MVP in Hyper-V
  • Author
  • Technical sales
  • Writer
  • Lead on Azure IaaS
  • MVP in Azure

And now I can see somewhat of a return to development. I don’t see myself coding, but I’m heading to Ignite with the intention of spending as much time as posisble learning PaaS stuff, while trying to figure out what’s happening in Windows Server 1709, Azure IaaS developments, and soooo much more!

Please follow and like us:

1 Comment on Year 10 as an MVP – Adding The Azure Expertise

  1. David mills // July 1, 2017 at 9:35 PM // Reply

    Congratulations! You deserve it. Thanks for all your help.

Leave a comment

Your email address will not be published.


*