DISCLAIMER: I am working towards my CCIE and this isn’t an emotional or knee-jerk reaction. For me the CCIE is only a stepping stone for the further expansion of my knowledge.
I woke up this morning to an interesting article written by friend Colin McNamara. Colin is an all around cloud evangelist promoting the leading and bleeding edge in cloud, automation and cultural change within IT. It isn’t the first time I have heard grumblings of the CCIE becoming less valued or out of touch with the industry but I wanted to respond to Colins post.
I agree with many points in his article and as I write this I have multiple python tabs open, I am looking at the VMware NSX API and have a few open documents on OpenStack integration. My role is slowly changing and I am right in the middle of seeing this. VMware NSX provides the ability to administrators of virtual environments to deliver programmatically delivered network constructs that change how we consume network functions. This can be done through a GUI (which uses the API ) , the RESTful API or an orchestration platform such as vCAC or Openstack. My role consists on understanding how to consume these, the network in the modern data center and how business benefit from such.
At some point, while monitoring for changes in their ability to earn money, these individuals saw the market, tech, whatever hit a tipping point.
Once at that point, their focus switched from monitoring the rate of change in their current skill set, to prepping to flip to the new cheese, the new cert, the new skill that will provide for them and their families for the next couple years.
The industry change is visible. For once we can see our industry changing right beneath us. The currents of change are pushing careers down different paths. Seeing this happening or if I be more accurate – choosing to see this happening – is something that will keep you ahead of the curve. The CCIE provides a great base standard of protocol knowledge mixed in with current and useful networking practices (I speak about the v5 blueprint!).
SDN, NFV, Cloud and devops all change the way we consume traditional function. We approach problem spaces in a new way with a different mindset. In this new world we have not re-written TCP/IP, we still consume IPv4 and IPv6 and deploy x86 workloads in software containers. What is changing is that no longer is big iron the way we do this or using the console to get into physical firewalls. No longer are we seeing us touching all the boxes across all sites manually. Change is programmatic and deployed across all devices. This gives us new scale and a new approach. Taking this to the new level are solutions like Distributed Firewall within NSX. Centrally managed and enforced via distribution in-kernel firewall uses the firewall technology in a different way.
Once you learn to enjoy the act of change, you will find that your perspective during tech transitions changes from fear, to wonder. That this world and industry is an amazing place.
I agree with Colin here. Embracing change is an absolute blast. Change doesn’t mean old skills are instantly or at all deprecated. A lot of times consumption methods change or we look at a problem in a differently but at the core we are looking to achieve the same end result.
I fully believe that the progression of technology will affect the hiring pool. I believe that the value that the CCIE currently holds will be replaced by the concept of “Network Developer”
I think the word replaced here is a bit dramatic and don’t agree entirely. I agree there is a progression in technology and that the hiring pool is seeking additional skills to the traditional acronym check list – BGP, MPLS, CCIE, CCNP, JNCIE. We are adding DevOps, Continuous Integration, Puppet, Chef and the like. We are adding Python and a language to this. We might see ACI or NSX or Contrail pop on here in time but I feel supplementing or core knowledge fields shouldn’t be about a product solely. It needs to be around a movement, technology, trend and the consumption of this.
The CCIE still gives a very robust knowledge platform in the networking space. What is important to remember that if you do not evolve from here and compliment core knowledge and diversify with a programming language or another technology you may go stale. If you become complacent with the notion that CCIE is the end-goal then you’re sorely mistaken. Someone who doesn’t develop on their CCIE will be looking for work at Taco Bell in time. Choosing not to evolve is what will break you not the advent of new technologies.
Colin draws on some childhood experience about changing through work, jobs and adapting to survive. Coming from little and appreciating providing for his family have driven him to not return to a place. Change has become a means to be the best and is fuel by knowing first hand what awaits for those that don’t. This context adds the reality to the situation.
I agree with change and the majority of what Colin is saying. Look where I am now. I moved from enterprise into VMware’s networking division working with disruptive network technologies. I want to boost my current depth of practical protocol knowledge too whilst learning API consumption. I too refuse to be the Lilliputian and want to always hunt for my cheese. I do owe Colin a beer or two and a beard rubbing next time I see him.