A recent twitter comment or should I say declaration by Craig Kilborn reminded me that I wanted to write a posting about doing the VCDX for the right reasons (Disclaimer: this is my opinion and if you disagree then that is perfectly fine). Also I am really looking forward to the posting Craig is going to put out as he was and still is one of the most prepped people I know for the VCDX defences yet sadly failed it.
When people come up to me at conferences or VMUG’s and chat to me about my VCDX journey and my achieving the VCDX accreditation and state they are looking to start the journey towards getting a VCDX number I always ask them one initial question: Why do you want the VCDX accreditation? The VCDX and path has been an amazing experience and learning curve for me and I know many many others and I personally feel you should do it for the cliché reason of “for the journey and not the destination” as the amount you need to learn and the breadth of not just technical skills but also public speaking, white boarding skills, stress management skills and the biggest one I had – realising how little you actually know and still need to learn is the best reason to do it. I know I ruffled a few VCDX feathers on a Geek Whisperers podcast appearance I did where I stated that getting the VCDX won’t always mean you will get a top role at VMware or get that six figure salary or automatically get that promotion. But the skills you have learnt and perfected along the way to obtaining your VCDX might bring some of those. I still believe this and if you do it for those reasons you might be disappointed once you get your number.
I use certifications to force myself to learn new technologies and for me the VCDX track was something that was going to push me to learn VMware technologies to a level only a certain amount of people globally had “proven” this level of knowledge. What I didn’t realise was that the VCDX was going to force me to not just know VMware technologies to an expert level but also all the supporting technologies around it and how the VCDX requires people to have a very strong holistic understanding of all the technologies in a solution and how differing decisions can/would have impacts on the success of the design/solution. So even though this might sound a level that is daunting to you (it was certainly for me and to be honest it still is a work in progress due to the ever changing landscape of IT) the amount you learn about all the supporting technologies, from people also aiming for the certification as well as the community around it is priceless and for me has been the main “prize” of doing the VCDX.
Last year October I defended a vRealize Automation design I had done in my spare time for a real world customer along with the infamous Rene van den Bedem and Andrea Siviero to hopefully obtained my VCDX6-CMA. I was ultimately unsuccessful in this attempt but gained an untold amount of experience not just from building a VCDX level design for vRA along with the required supporting documentation but again realising where there were gaps in my knowledge that needed to be filled. One of these was NSX where I knew a certain working level but in hindsight I naively should have realised the amount NSX played a part in our solution and even though the defence was about vRA the impacts on the decisions and design we had made for NSX was a direct influencer on if the solution succeeded or failed. From this I have been up skilling on NSX and last week Friday I passed the first step in this by obtaining my VCP6-NV. I will also most likely resubmit for my VCDX6-CMA in the future because 1. I seem to be a masochist and 2. I fully believe a quote from a video I used to watch in prep for my VCDX-DCV second defence of “Pain is temporary, it may last for a minute, or an hour, or a day or even a year but it will subside, if you quit however the pain will last forever” and I can’t help myself but want to complete what I started or else I am accepting the failure. From needing to better my knowledge of NSX I have seen a direct impact and benefit to my role as a Solution Lead in Dell EMC’s Cloud Practice and the methods I learnt and used for my DCV and CMA submissions have proven untold benefit on the deliveries I have had to produce on projects I have worked on.
I’ve possibly been as clear as mud in this posting but my main personal thoughts and opinions about wanting to go for the VCDX are:
- Do it as it has been an amazing learning experience and continues to be for me.
- Don’t be afraid to fail it as for me it has been the best way to truly show me where I need to be better.
- Do it to be a better architect and have a more well rounded knowledge as the IT landscape is forever changing and you never know when one of those supporting technology skills will maybe get your foot in the door to a new exciting opportunity
- The community around the VCDX is amazing and 98% of VCDX’s are more than willing to help you along your journey but you have to take the initiative as no one is going to carry you. As Rebecca Fitzhugh a relatively recent VCDX wrote about, a good mentor never coaches you but challenges, encourages and provides “wisdom” when needed.
- There is a fair likelihood that once you achieve the VCDX your company and/or boss will have no idea what it really means and most recruiters are more excited about someone being a vExpert than a VCDX but the skills you learnt in the journey towards VCDX will be what might get you that new role or promotion but don’t do the certification for those reasons as you might be disappointed that not much changes initially if possibly at all once you get a VCDX number. It’s actually one of the reasons I ask “ Life after the VCDX? How did your company respond? Was it worth it?” in my VCDX Spotlight postings as for most the change is minor and might only happen a fair time later.
- There is a substantial amount of personal time and effort that goes into the journey and if you don’t use it for all the lessons along the way then once you achieve it you might be saddened by what is behind the Wizard of VCDX’s curtain.
If you are realistically aiming for the VCDX(You have the VCAp’s/VCIX in your chosen track or are on the cusp of having them) then I run a VCDXPrepGroup slack channel where people also aiming for the VCDX can work together and where we have almost a dozen VCDX mentors covering all four of the tracks. Message me and I’ll add you to the group but be warned the group won’t give you anything that will break the NDA’s and you won’t be supplied people’s VCDX submissions so you will have to put in the work, the group just provides the platform to get some valuable feedback and link you to fellow VCDX Wannabe’s.
Lastly good luck to those that defended VCDX this week (a fair few from the slack group) and for those aiming for future defences good luck on the journey.